Communications management using down link control information

ABSTRACT

Downlink Control Information (DCI) may be expanded, or enhanced, to allow nodes such as UEs, eNBs, NR-nodes, gNBs, and TRPs in M2M, IoT, WoT networks to coordinate activities on PHY, MAC, and RRC layers. For example, DCI fields may be added or enhanced to include, for example, information regarding time resource allocation, frequency resource allocation, mini-slot allocation, and or Code Block Group (CBG) transmission. Such information, or similar information, may be used in operations such as mini-slot operations, Code Block Group (CBG) transmission, group common Physical Downlink Control Channel (PDCCH), grant-free and grant-less operations, response to Beam Failure Recovery Request (BFRR), UL Transmit (TX) beam change, Quasi-Co-Location (QCL) operations, aperiodic CSI-RS transmission and interference measurement, Band Width Part (BWP) operations, and Multi-Transmission and Reception Point (TRP)/Multi-Panel.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/556,070, filed on Sep. 8, 2017, entitled “Communications managementusing down link control information,” the content of which is herebyincorporated by reference in its entirety.

BACKGROUND

In LTE, Downlink Control Information (DCI) is formed, and transmitted ina Physical Downlink Control Channel (PDCCH) or an Enhanced DownlinkControl Channel (EPDCCH), to signal to the UE how to receive its data ona Physical Downlink Shared Channel (PDSCH) or transmit its data on aPhysical Uplink Shared Channel (PUSCH) in a subframe. See, for example,3GPP TS 36.212, Multiplexing and channel coding (Release 14), V14.3.0.An LTE DCI may transport downlink, uplink or sidelink schedulinginformation, requests for aperiodic Channel Quality Indicator (CQI)reports, Licensed-Assisted Access (LAA) common information, andnotifications of Multicast Control Channel (MCCH) change or uplink powercontrol commands for one cell and one Radio Network Temporary Identifier(RNTI) for a User Equipment (UE), for example. The RNTI is implicitlyencoded in the Cyclic Redundancy Check (CRC), so that only the UE withthe RNTI may decode the DCI format, and hence use the correspondingPDSCH. The packed DCI information is the payload to the PDCCH encodingchain. The DCI formats are further classified as downlink DCI formatsand uplink DCI formats as detailed in 3GPP TS 36.212.

SUMMARY

Downlink Control Information (DCI) may be expanded, or enhanced, toallow nodes such as UEs, eNBs, NR-nodes, gNBs, and TRPs in 3GPP networksto coordinate activities on PHY (physical layer), MAC (medium accesscontrol layer), and RRC (radio resource control layer). For example, DCIfields may be added or enhanced to include information regarding timeresource allocation, frequency resource allocation, mini-slotallocation, and/or Code Block Group (CBG) transmission. Suchinformation, or similar information, may be used in operations such asmini-slot operations, Code Block Group (CBG) transmission, group commonPhysical Downlink Control Channel (PDCCH), grant-free or grant-lessoperations, response to Beam Failure Recovery Request (BFRR), ULTransmit (TX) beam change, Quasi-Co-Location (QCL) operations, aperiodicCSI-RS transmission and interference measurement, Band Width Part (BWP)operations, and Multi-Transmission and Reception Point(TRP)/Multi-Panel.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE FIGURES

A more detailed understanding may be had from the following description,given by way of example in conjunction with accompanying figures.

FIG. 1A illustrates an example communications system.

FIG. 1B is a block diagram of an example apparatus or device configuredfor wireless communications such as, for example, a wirelesstransmit/receive unit (WTRU).

FIG. 1C is a system diagram of a first example radio access network(RAN) and core network.

FIG. 1D is a system diagram of a second example radio access network(RAN) and core network.

FIG. 1E is a system diagram of a third example radio access network(RAN) and core network.

FIG. 1F is a block diagram of an exemplary computing system in which oneor more apparatuses of communications networks may be embodied, such ascertain nodes or functional entities in the RAN, core network, publicswitched telephone network (PSTN), Internet, or other networks.

DETAILED DESCRIPTION

Table 1 of the Appendix lists many of the acronyms used herein.

A number of challenges are presented by New Radio (NR) architectures. Afirst problem is that, as more new functions have been introduced intoNR system, more physical layer signaling is required for the accessnetwork to direct a UE to receive and transmit its data efficiently. Howto categorize the control information required for new radio, and how tooptimize the DCI design for a NR system, are fundamental problems forcontrol signaling design.

A second challenge is that beamforming may be used in NR to provideenough cell coverage and high throughput. Due to the directional natureof beamforming, beam failure may happen more frequently than, forexample, radio link failure in LTE. To enable quick and efficient beamfailure recovery, Layer 1 signaling-based beam failure recoverymechanisms may be used in NR. A UE may transmit its beam failurerecovery request on PUCCH or PRACH, and the gNB may send its response toits beam failure recovery request on a PDCCH to the UE, for example.

A third challenge is how to reduce signaling and reporting overhead formassive MIMO design. For example, how to make the best use of aQuasi-Co-Location (QCL) property, and how to optimize the Channel-StateInformation-Reference Signal (CSI-RS) functions, are importantquestions.

A fourth challenge is how to design DCI in NR to dynamically configurethe Band Width Part (BWP) needs to be addressed for wide band operationsin a NR system. In addition, how to use QCL property to optimizemulti-TRP and multi-panel design needs to be solve for a NR system.

To address these and other challenges, DCI fields may be added orenhanced to support, for example, time resource allocation, frequencyresource allocation, mini-slot allocation, or Code Block Group (CBG)transmission. Such information, or similar information, may be used inoperations such as mini-slot, group Common PDCCH, grant-freecommunications, Response to Beam Failure Recovery Request (BFRR), ULTransmit (TX) beam change, Quasi-Co-Location (QCL), aperiodic CSI-RStransmission and interference measurement, Band Width Part (BWP), orMulti-Transmission and Reception Point (TRP)/Multi-Panel.

New or enhanced DCI formats may be used in various RAN architectures,where they are used in processes implemented by, for example, an NR-nodeor gNB, Transmission and Reception Point (TRP), or Remote Radio Head(RRH), as well as the central controller in RAN or control function in aRAN slice. Such formats and operations may be used equally in grant-freeor grant-less operations, for example.

Parameters may be used for Time Resource Allocation (TRA). TRA may becontiguous or noncontiguous. Noncontiguous TRA may be evenly distributed(herein termed “periodic”) or unevenly distributed (herein termed“distributed”).

Time resource may be allocated dynamically with DCI per slot/subframefor slot/subframe based scheduling, or multi-slot/multi-subframe forslot/subframe aggregated scheduling. For slot/subframe aggregated timeresource allocation, more than one set of allocation may be included ifeach allocation of aggregated slot/subframes is different, for exampletime resource allocation set 0, for example TRA0, is for slot 0/subframe0, and time resource allocation set 1, for example TRA1, is for slot1/subframe 1, etc. Note, either slot or subframe based may be indicatedin the System Information (SI) or configured by RRC signaling.

For multi-link scenarios, such as multi-BWP, multi-TRP, multi-carrier,or multi-RAT connections, etc., the time resources may be allocatedjointly with DCI(s) on one NR-PDCCH, for example, a joint CORESET(Control Resource Set), or separately with DCIs on more than oneNR-PDCCH, for example, different CORESETs respectively. If allocatedjointly by one NR-PDCCH, more than one set of allocation may be used ifeach allocation of multi-BWP, multi-TRP, multi-carrier, or multi-RATconnections is different, for example time resource allocation set 0,for example TRA0, is for BWP 0/TRP 0/Carrier 0/RAT 0, and time resourceallocation set 1, for example TRA1, is for BWP 1/TRP 1/Carrier 1/RAT 1,etc.

An example of time resource allocation is described in Table 2 of theAppendix, which may be indicated by DCI field(s) explicitly or indicatedby DCI field(s) implicitly, e.g., using the bitmap or index of the timeallocation from a set or multiple sets of time allocations.

A set or subset of the TRA parameters exemplified in Table 2 may beadded into the current LTE DCI format 0/1/1A/1B/1C/1D/2/2A/2B/2C fortime resource allocation feature. However, a set or subset of the TRAparameters exemplified in Table 2 may be also used to form a new DCIformat, for example a DCI format for mini-slot allocation within a slotor subframe which is exemplified in Table 4, Table 6 and Table 7 of theAppendix.

A parameter or parameters may be used for Frequency Resource Allocation(FRA). FRA may be contiguous or noncontiguous. For noncontiguous, it maybe evenly distributed with the same size of segments and a gap betweenthe segments, or unevenly distributed with different sizes of segmentsand different gaps between the segments.

Frequency resource may be allocated dynamically with DCI in the unit ofPhysical Resource Block (PRB), for example 12 subcarriers, or in theunit of Resource Block Group (RBG) where the RBG is m consecutive PRBsbased on the RBG_size=m which may be indicated in the System Information(SI) or configured by RRC signaling.

For multi-link scenarios, such as multi-BWP, multi-TRP, multi-carrier,or multi-RAT connections, etc., the frequency resources may be allocatedjointly with DCI(s) on one NR-PDCCH (for example, a joint CORESET) orseparately with DCIs on more than one PDCCH (for example, on differentCORESETs respectively). Either allocated jointly or not by one NR-PDCCH,more than one set of allocation may be used if each allocation ofmulti-BWP, multi-TRP, multi-carrier, or multi-RAT connections isdifferent, for example frequency resource allocation set 0, for exampleFRA0, is for BWP 0/TRP 0/Carrier 0/RAT 0, and frequency resourceallocation set 1, for example FRA1, is for BWP 1/TRP 1/Carrier 1/RAT 1,etc.

An example of parameters for frequency resource allocation is describedin Table 3 of the Appendix, which may be indicated by DCI field(s)explicitly or indicated by DCI field(s) implicitly, e.g., using thebitmap or index of the frequency allocation from a set or multiple setsof frequency allocations.

A subset of the FRA parameters exemplified in Table 3 may be added intothe current LTE DCI format 0/1/1A/1B/1C/1D/2/2A/2B/2C for frequencyresource allocation, especially for the noncontiguous allocation forCP-OFDM waveform. However, a set or subset of the FRA parametersexemplified in Table 3 may be also used to form a new DCI format, forexample a DCI format for activating/deactivating a BWP which is exampledin Table 10B of the Appendix.

A time allocation parameter or parameters may be used for mini-slotallocation in time. A 1˜7 symbol mini-slot may be inserted at eachsymbol of a slot. The mini-slot allocation may be signaled by a DCI. Anexample is shown in Table 4 of the Appendix.

A subset of the FRA parameters exemplified in Table 3 may be added intothe current LTE DCI format 0/1/1A/1B/1C/1D/2/2A/2B/2C for mini-slotallocation in frequency. However, a set or subset of the mini-slotallocation parameters exemplified in Table 2 and Table 4 may be alsoused to form a new DCI format, for example a DCI format for mini-slotwhich is exemplified in Table 6 for an uplink mini-slot and Table 7 fora downlink mini-slot in the Appendix.

A DCI field may be used for CBG transmission with the parameters asexemplified in Table 5 of the Appendix.

A subset of the CBG parameters exemplified in Table 5 may be added intothe current LTE DCI format 0/1/1A/1B/1C/1D/2/2A/2B/2C for CBG based(re)transmissions. However, a set or subset of the parameters may bealso used to form a new DCI format, for example a DCI format for CBGtransmission.

DCI formats may be adapted for use with mini-slot(s). A light DCIstructure is desired for fitting into the limited symbol resources of amini-slot if the DCI is allocated within the mini-slot as well as forreduced latency. Examples of DCIs for a mini-slot are shown in Table 6for an uplink minis-lot and Table 7 for a downlink mini-slot of theAppendix.

A UL or DL mini-slot DCI may be carried by a UE specific NR PDCCH for aUE or by a group common PDCCH for a group of UEs. A compact version ofthe DCI, exemplified in Table 6 and Table 7, for DL mini-slot may alsobe inserted into a DL mini-slot (for example, the mini-slot occasion)which is indicated by the mini-slot allocation DCI described in Table 4or configured by RRC.

A UE blindly decodes the UL or DL mini-slot DCI carried on the NR-PDCCHin a UE specific searching space allocated either at the beginningsymbols of a slot or subframe or at UE's mini-slot occasions (forexample within a mini-slot), with the UE's C-RNTI or Temp-C-RNTI, orcarried on the group common PDCCH for a group of UEs in a group commonsearching space with the UE's Group Common-RNTI (GC-RNTI).

Once the UE has successfully decoded the DL mini-slot DCI(s), UE mayconduct data reception within a mini-slot. Where there is no DCI in themini-slot, this may involve receiving the DL data and DMRS on PDSCHscheduled at the allocated mini-slot(s) by the decoded DCI(s) allocatedat the beginning symbols of a slot or subframe, for example, themini-slot DCI with C-RNTI, TC-RNTI or GC-RNTI, estimated the channelusing the DMRS, and demodulate and decode the received data per the MCS,TPMI/PMI, etc., and then conduct HARQ combining with retransmissionsbased on the HARQ process number, NDI, RV, etc. for the data informationbits. Also, conducts the HARQ Acknowledgment feedback (for exampleHARQ-ACK) per the HARQ-ACK resource parameter. Where there is one ormore DCIs in the mini-slot(s) with C-RNTI or TC-RNTI, this may involvedetecting the DCI at the allocated mini-slot(s) to check if there is anyDL data scheduled in that mini-slot. If there is a DL data scheduled atthis mini-slot, then the UE conducts channel estimation, demodulation,decoding, and HARQ combining for retransmissions, etc. for the datainformation bits, as well as the HARQ-ACK feedback.

Once the UE has successfully decoded the DL mini-slot DCI(s) carried onNR-PDCCH or GC-PDCCH allocated either at the beginning symbols of a slotor subframe or PDCCH at UE's mini-slot occasions (for example within amini-slot), UE may additionally or alternatively conduct measurementswithin the mini-slots. Where there is no DCI in the mini-slot, the UEmay conduct the measurement procedure using the Reference Signal in themini-slot indicated by the DCI, carried by the NR-PDCCH or GC-PDCCH atthe beginning symbols of a slot or subframe, of the measurementreference signal resource configurations by RRC. For example, thereference signals such as CSI-RS based beam training, mobilitymeasurement, time or frequency tracking and correction, or Channel StateInformation (C SI) measurement, etc. Where there is DCI in themini-slot, the UE may detect the DCI at the allocated mini-slot(s) tocheck if there is any DL RS configured in that mini-slot formeasurement. If there is a DL RS configured at this mini-slot, then theUE conducts measurements with the RS per the configuration in the DCIdetected in the mini-slot.

Regarding multiple DCI contents, if the DCI content in a mini-slotconflicts with the mini-slot DCI carried by NR-PDCCH or GC-PDCCH at thebeginning symbols of a slot or subframe or RRC configuration, the DCI inthe mini-slot may override the DCI on NR-PDCCH or GC-PDCCH or RRCconfiguration. For multiple mini-slots, the DCI in each mini-slot takesthe highest priority. For a mini-slot without DCI inserted (for example,an aggregated mini-slot transmission over more than one mini-slot), theprevious mini-slot's DCI, if presented in time after the NR-PDCCH orGC-PDCCH at the beginning symbols of a slot or subframe, may be applied,otherwise the DCI of NR-PDCCH or GC-PDCCH may be applied.

A new DCI format may be designed for use with a group common PDCCH,where the group common PDCCH is used for signaling the slot format to agroup of UEs. An example is shown in the Table 8A of the Appendix.

In Table 8B an example is provided for slot format indication of up to2′ slots.

A group common PDCCH may indicate preemption to eMBB UEs.

Table 8C provides an example of the configuration of such a DCI whereinthe starting resources and number of resources (symbols in time and RBsin frequency) from the start are configured in the DCI.

Table 8D provides an example of the configuration of such a DCI whereinthe starting resources (symbols in time and RBs in frequency) areconfigured in the DCI by x and y are configured through RRC.

Table 8E provides an example of the configuration of such a DCI whereinthe starting symbols in time and k sets of contiguous RBs of granularityy in frequency are configured in the DCI. The k sets of RBs may becontiguous or discontinuous in frequency. Here x and y are configuredthrough RRC.

A UE may be configured or assigned with one or more Group Common RNTIs(GC-RNTIs), for example a value of (0000)₁₆˜(FFFC)₁₆, that may becarried in the group common PDCCH. For example, the scrambling code inthe DCI may be initialized or its CRC is scrambled with the GC-RNTI ofthat DCI. When a UE uses its GC-RNTI to scramble the DCI, it maycorrectly decode its Group Common-PDCCH (GC-PDCCH).

A GC-PDCCH carrying the SFI may be transmitted both in a common CORESETconfigured by the PBCH and/or in a UE-specific CORESET. When a UE is atRRC Idle or RRC Inactive state, it may blind decode the common CORESETconfigured by the PBCH, for example in the common searching space, forSFI information. When a UE is at RRC Connected state, it may monitor theGC-PDCCH on the UE-specific CORESET, for example in the UE specificsearching space, if it is configured or in the common CORESET in thecommon searching space.

Multiple GC-PDCCHs may be sent in the same monitoring occasion of a UE.The different GC-PDCCHs may have the same GC-RNTI or different GC-RNTIs.For example, the gNB may send 2 GC-PDCCHs in one or two CORESETs withthe same or different GC-RNTI for different purposes—one for indicatingthe SFI and another for indicating preemption.

If a UE receives multiple GC-PDCCHs either in the same or differentmonitoring occasions and the GC-PDCCHs contain conflict content, the UEmay prioritize one over another.

For example, a GC-PDCCH in slot N may indicate a SFI applicable to theremaining R slots in a radio frame. Then it may receive another GC-PDCCHin slot N+1 indicating a different SFI applicable to the remaining R-1slots in the frame—in this case the UE may prioritize the most recentGC-PDCCH.

Another example is that a UE detects one GC-PDCCH in the commonsearching space and one GC-PDCCH in the UE specific searching space,then the UE may choose the GC-PDCCH detected from the UE specificsearching space if the detected GC-PDCCHs contain conflict content.

Another example is that when a UE operates with two TRPs and receivesone GC-PDCCH from each TRP in the same searching space with conflictcontent, the UE may prioritize in a number of ways. For example, if oneof the TRPs is from the primary cell and the other from secondary cell,the UE follows the GC-PDCCH from the primary cell. If one of the TRPs(or its beam) is designated as the primary beam, the UE follows theGC-PDCCH from the primary TRP beam. If UE has a grant from one of theTRPs, it prioritizes the GC-PDCCH from that TRP.

If the UE fails to detect a GC-PDCCH, it uses the default configuration.For example, if it does not receive or failed to decode the SFI from aGC-PDCCH, it may use a default configuration indicated through systeminformation.

DCI formats may be designed for use in grant-free resource allocation.An example is shown in Table 9 of the Appendix.

A DCI may be designed for HARQ/ACK feedback for grant-freecommunications as an example. An example is shown in Table 10A of theAppendix.

Grant-free DCIs may be carried by a UE specific NR-PDCCH allocated atthe beginning symbols of a slot or subframe or allocated at mini-slotoccasions configured for grant-free transmissions for a UE or by a groupcommon PDCCH for a group of UEs. A UE blindly detects the Grant-freeDCIs carried on an NR-PDCCH in a UE specific searching space with theUE's C-RNTI or Grant-Free-RNTI (GF-RNTI) assigned by the gNB during theAttachment procedure at Initial Access stage or RRC Connect procedurewhen switching from RRC-Idle or RRC-Inactive to RRC-Connect state. A UEmay also blindly detect the Grant-free DCI(s) carried on a group commonPDCCH for a group of UEs in a group common searching space with the UE'sGroup Common-RNTI (GC-RNTI) or Grant-Free-RNTI (GF-RNTI) assigned by thegNB during the Attachment procedure at Initial Access stage or RRCConnect procedure when switching from RRC-Idle or RRC-Inactive toRRC-Connect state.

Once the UE successfully decoded the grant-free DCIs, UE is ready toconduct the UL grant-free data transmission per the resource allocation,MCS, etc. indicated the DCI Format 0D in Table 9 with the Layer 1activation DCI in Table 10B of the Appendix, where the transmission maybe slot or subframe based or mini-slot based.

For initial transmission, a UE may set the initial transmit power basedon the path loss measurement using the Synchronization Signal (SS) orCSI-RS on DL or DMRS in the NR-PDCCH or GC-PDCCH carrying the grant-freeDCI(s). UE may also set the initial transmission power based on theGroup based UL power setting carried on the DCI Format 3/3A as anexample, or RRC signaling for power setting from gNB.

For retransmission, the UE may set the transmit power based on path lossbased open loop power control, or based on the feedback from the gNB inthe TCP command for PUSCH in the DCI Format 0D in Table 9.

The UE may set the Timing Advance for UL time adjustment during theAttachment procedure at Initial Access stage or RRC Connect procedurewhen switching from RRC-Idle or RRC-Inactive to RRC-Connect state. TheUE may also make finer timing adjustment based on the DL receivedSynchronization Signals or time or frequency tracking Reference Signalor the DMRS on the NR-PDCCH carrying the grant-free DCIs.

When there is a UL data passed from UE' higher layer, the UE encode andmodulates the data per the MCS etc. in the DCI Format 0D in Table 9, andthen transmits it on the resources as indicated by the time andfrequency resource allocation in the DCI Format 0D in Table 9 with theinitial transmit power. If repetition is enabled, the UE may repeatedlysend the same data at different time allocations as configured and atthe same or different PRB/RBG resources allocated with or withoutfrequency hopping using the same or different MCS and RV setting per theconfiguration in DCI Format 0D, till reaches the maximum repetitionnumber K or is timed out by higher layer timer (such as MAC layertimer), or receives a first ACK on the DCI carrying the HARQ-ACKfeedback from gNB. The UE may also adjust the transmit power with aconfigured incremental value for repetitions, if it's below the UE'smaximum allowable transmit power level.

If a NACK is received on the DCI carrying the HARQ-ACK feedbackexemplified in Table 10A, the UE may send the same Transport Block (TB)data from the higher layer at different time allocations as configuredand at the same or different PRB/RBG resources allocated with or withoutfrequency hopping using the same or different MCS and RV setting per theconfiguration in DCI Format 0D in Table 9 or grant based configurationfor UL transmission, till reaches the maximum retransmission number oris timed out by higher layer timer (such as MAC layer timer), orreceives a first ACK on the DCI carrying the HARQ/ACK feedback from gNB.The UE may adjust the power level per path loss for open loop powercontrol or TCP command piggybacked on the HARQ-ACK feedback for closedloop power control. The UE may also adjust the Timing Advancement for ULper the TA piggybacked on the HARQ-ACK feedback.

The UE may also be indicated to transmit UL Control Information (UCI) onPUCCH and/or Sound Reference Signal (SRS) without the PUSCH (for exampledata) using the similar procedures as the above.

HARQ-ACK feedback may be used. After each UL transmission, the UE maydetect the grant-free DCI for HARQ-Ack feedback carried by either: a UEspecific NR-PDCCH for a UE in UE specific searching space using the UE'sC-RNTI or GF-RNTI which may be allocated at the beginning symbols of aslot or subframe or allocated at mini-slot occasions configured forgrant-free transmissions; a group common PDCCH for a group of UEs ingroup common searching space using GF-RNTI or GC-RNTI; or a commonsearching space indicated by broadcasting channel such as PBCH usingTemp-C-RNTI, C-RNTI or GF-RNTI. The HARQ ID derived from the time,frequency and/or UE ID may also be used for scrambling the HARQ-ACK DCIif the UE derives it and piggy-backs it on its UL grant-freetransmission.

For multiple DCI contents, if a common or UE specific DCI contentcarried in a NR-PDCCH or GC-PDCCH conflicts with the GF-DCI, the DCI(s)in the GF-DCI override the DCI on NR-PDCCH or GC-PDCCH. If multiple GFDCIs are activated, the latest one takes the highest priority. If theGF-DCI(s) are deactivated, then a UE may only conduct grant-free ULtransmission fully configured per the RRC signaling. If the UE detects aresponse from the gNB with GF-DCI(s) activated following its initial RRCconfigured grant-free transmission, then it may use the configurationactivated by the received GF-DCI(s) for repetition, retransmission orfor following new data transmission(s).

DCI formats may be adapted to support beam failure recovery. Forexample, DCI formats may be adapted to support a gNB's response to aBeam Failure Recovery Request (BFRR), a gNB initiated UL TX Beam change,and for corresponding UE behaviors.

A new DCI format, such as format 7A described herein, may be used tosignal the gNB's response to beam failure recovery request.

DCI for a response to a beam failure recovery request may include a D LTX beam confirmation. For example, where a UE reports only one candidatenew beam, one bit may be used to indicate whether the new candidate beamreported in UE's BFRR may be used as gNB's TX beam or not. See Table 10Cof the Appendix.

Where a UE reports multiple candidate new beams, then N bits may be usedto indicate whether one of new candidate beams (up to 2′) reported inUE's BFRR may be used as gNB's TX beam or not. An example of N=2 isshown in Table 10D of the Appendix.

DCI for a response to a beam failure recovery request may include afield for beam reporting in UL. For example, such a field may be used ifa DL beam confirmation bit field indicates that none of new candidatebeams reported in UE's latest BFRR may be used or there are no newcandidate beams reported in UE's latest BFRR.

DCI for a response to a beam failure recovery request may include afield for CSI-RS allocation in the DL. This may include an indication ofone CSI-RS resources pattern out of the M CSI-RS configurations signaledby RRC signaling, and additionally or alternatively include a timingoffset and repetition of the DL CSI-RS transmission.

DCI for a response to a beam failure recovery request may include afield for UL resources of PUCCH for beam reporting. This may include anindication of PUCCH resources of the format used for beam reporting. Forexample, if Q potential PUCCH resources are configured by RRC signalingor specified in the standards. Then, [log₂ ^(Q)] bits may be used forthis field.

This may additionally or alternatively include a timing offset of beamreporting on the indicated PUCCH resources: the value of timing offsetmay be signaled either implicitly or explicitly. For implicit signaling,for example, the timing offset of beam reporting on PUCCH is a fixedvalue after the last CSI-RS instance indicated in the DCI format 7A. Forexplicit signaling, for example, K1 kits indicates 2^(K1) possibletiming offsets.

This may additionally or alternatively include a number of beamreporting DCI for a response to a beam failure recovery request mayinclude UE ID. An example of DCI format 7A is shown in the Table 11 ofthe Appendix.

After a UE detects a beam failure and transmits a beam failure recoveryrequest (BFRR) to the gNB, the UE may monitor a PDCCH format 7A wheregNB's response to BFRR is signaled in the common and UE-specific searchspaces within a certain time window. For a valid PDCCH format 7A that isdetected, UE may obtain the gNB's response to the latest BFRR ittransmitted. The UE may use this information to update the DL TX Beam inthe beam pair link (BPL) between the gNB and the UE. Alternatively, theUE may perform beam measurement per DCI format 7A.

The UE may use the information of DL TX beam confirmation to knowwhether the gNB may use one of the new candidate beams reported in theUE's latest transmitted BFRR. If yes, the UE may use the confirmed DL TXBeam in the BPL between the gNB and the UE.

If no, the UE may perform CSI-RS measurement and beam reporting to helpthe gNB to determine a new DL TX beam. The UE may obtain the CSI-RSmeasurement related information to perform CSI-RS measurement asindicated in “CSI-RS allocation” field in the received DCI format 7A.Then, it performs beam reporting per the “UL resources of PUCCH for beamreporting” in the received DCI format 7A. Upon receiving the beamreporting from the UE, the gNB may determine a new DL TX Beam and notifythe UE.

A DCI format, such as format 7B described herein, may be used toindicate or carry signaling for a UL TX beam change initiated, forexample, by a gNB. For example, the DCI information may carry a UE ID.

DCI information may be used, for example, in various methods may be usedto indicate a UL TX beam change. A first way to indicate a UL TX beamchange is for one bit to be used to indicate whether a new UE's TX beamshould be used, decided by gNB's measurement of UE's uplink DMRS andSRS. A second way is for two bits to be used for UL TX beam changeinformation. The first bit may be used to indicate whether the UL TXbeam should be changed. The second bit may indicate either gNB mayindicate a new UL TX beam or gNB may send a SRS request for UE totransmit SRS so that gNB may perform measurement and determine a new ULTX beam.

Similarly, a DCI format, such as format 7B, may be used to indicate orcarry signaling for a new UL TX beam. For example, a UL new TX beamfield may be used where the UL TX beam change indication field indicatesa change. The field carries an identification of the new TX beam for theUE in the uplink

A DCI format, such as format 7B, may be used to indicate or carrysignaling for SRS transmission. For example, an SRS transmission fieldmay be used where the UL TX beam change indication field indicates nochange, and include an indication of UL TX beams that the UE should useto transmit SRS. For example, suppose that R sets of SRS configurationsare configured by RRC signaling or specified in the standards. If eachSRS configuration contains a subset of UL TX beams and SRS patterns,then └log₂ ^(R)┐ bits may be used for an SRS transmission field.

A field may be used to indicate the timing offset of SRS on indicated ULTX beams. This field may contain: the value of timing offset may besignaled either implicitly or explicitly. In implicit signaling, forexample, the timing offset may be a fixed value after the received UL TXBeam Change DCI format 7B. For explicit signaling, K5 bits may be usedto indicate 2^(K5) possible timing offsets.

A field may be used to indicate a number of SRS transmissions. Forimplicit signaling, for example, a number of SRS on a given UL TX beamequals to a number specified in the standards, for example, one. Forexplicit signaling, for example, K6 bits may be used to indicate one of2^(K6) possible numbers of SRS transmission.

Note that signaling related to UL TX Beam change may be piggybacked inDCI format 7A or other UL/DL grant DCIs.

An example of DCI format 7B is shown in the Table 12 of the Appendix.

A UE may monitor a PDCCH format 7B periodically or other DCIs such asUL/DL grants with DCI format 7B contents piggybacked in the common andUE-specific search spaces within a certain time window. For a validPDCCH format 7B or UL/DL grant with DCI format 7B contents piggybackedthat is detected, UE may obtain the gNB's initiated UL TX beam changeinformation. The UE may use this information to update the UL TX Beam inthe BPL between the gNB and the UE. Or the UE may transmit SRS per DCIformat 7B.

The UE may use the information of UL TX beam confirmation to knowwhether the gNB may indicate a new UL TX beam for the UE. If yes, the UEmay use the indicated UL TX Beam in the BPL between the gNB and the UE.

If no, the UE may transmit SRS to help the gNB to determine a new UL TXbeam, and the UE may transmit SRS per the SRS transmission relatedinformation as indicated in “SRS transmission” field in the received DCIformat 7B. It may follow the signaled SRS configuration, timing offset,and number of transmissions. Upon receiving the SRS from the UE, the gNBmay determine a new UL TX Beam and notify the UE.

DCI may be adjusted to support QCL indication, QCL checking indication,aperiodic CSI-RS transmission, and aperiodic interference measurement.The following signaling may be carried in DCI by either enhancingexisting DCI fields or using new DCI formats: PDSCH quasi-co-locationindicators; PDCCH quasi-co-location indicators; quasi-co-locationchecking indicators; aperiodic CSI-RS triggering indicators; aperiodicCSI-RS resource indicators; and Aperiodic Interference MeasurementResource (IMR) triggering indicators. Examples of the number of bitsneeded and description of each of these indicators are shown in Table 13of the Appendix.

A set or subset of the DCI field parameters in Table 13 may be addedinto the current LTE DCI format 0/1/1A/1B/1C/1D/2/2A/2B/2C forcorresponding function. However, a set or subset of the DCI parametersin Table 13 may be also used to form a new DCI format.

PDSCH resource mapping may be used with quasi-colocation of antennaports. A UE may be configured up to 8 parameter sets containing the QCLinformation of the DMRS for PDSCH by higher layer signaling to decodePDSCH per a detected PDCCH with DCI(s) intended for the UE.

The UE may use the parameter set list in the DCIs according to the valueof the PDSCH Quasi-Co-Location Indicator field (mapping defined in Table14 of the Appendix for 1 bit field scenario, Table 15 of the Appendixfor 2 bits field scenarios, Table 16 of the Appendix for 3 bits filedscenario) in the detected PDCCH with DCIs for determining the QCLrelationship of the DMRS for PDSCH with other reference signals.

A UE may be configured with one or two DMRS port group(s) based on thenumber of PDSCH that is monitored. When a UE is configured with one DMRSport group, if the PDSCH Quasi-Co-Location Indicator field is 1 bit,state ‘0’ is configured; if the PDSCH Quasi-Co-Location Indicator fieldis 2 bits, one of the state ‘00’, ‘01’ is configured; if the PDSCHQuasi-Co-Location Indicator field is 3 bits, one of the state ‘000’,‘001’, ‘010’, ‘011’ is configured. Each state refers to one RS set,which indicates a QCL relationship for the DMRS port group.

When a UE is configured with two DMRS port groups, if the PDSCHQuasi-Co-Location Indicator field is 1 bit, state ‘1’ is configured; ifthe PDSCH Quasi-Co-Location Indicator field is 2 bits, one of the state‘10’, ‘11’ is configured; if the PDSCH Quasi-Co-Location Indicator fieldis 3 bits, one of the state ‘100’, ‘101’, ‘110’, ‘111’ is configured.Each state refers to two RS sets where each RS set indicates a QCLrelationship for one of the two DMRS port groups of the UE respectively.

With different value of the PDSCH Quasi-Co-Location Indicator fieldconfigured, the UE may determine the QCL information for each DMRS portgroup such as which RS(s) is QCL-ed and the QCL-ed parameters for eachRS from the parameters in the corresponding parameter set configured viahigher layer signaling. Note, there may be one or more RS(s) with sameor different types in a RS set. If there are more than one RS in a RSset, each of them may associated with different QCL parameters.

A set or subset of the DCI PDSCH Quasi-Co-Location Indicator fieldparameters in Table 14, Table 15 and Table 16 may be added into thecurrent LTE DCI format 0/1/1A/1B/1C/1D/2/2A/2B/2C for indicating QCL forPDSCH DMRS. However, a set or subset of the above DCI parameters may bealso used to form a new DCI format, for example a DCI format forindicating QCL for PDSCH DMRS.

For one DMRS port group configured case, one or more of the followingparameters for determining PDSCH antenna port quasi co-location areconfigured via higher layer signaling for each parameter set:

qcl-CSI-RS-ConfigNZPId-NR.

qcl-CSI-RS-parameter-NR

qcl-SSblock-Index-NR.

qcl-SSblock-parameter-NR

qcl-PTRS-ConfigId-NR.

qcl-PTRS-parameter-NR

qcl-TRS-ConfigId-NR.

qcl-TRS parameter-NR

For two DMRS port groups configured case, one or more of the followingparameters for determining PDSCH antenna port quasi co-location areconfigured via higher layer signaling for each parameter set:

qcl-DMRSgroup1-CSI-RS-ConfigNZPId-NR.

qcl-DMRSgroup2-CSI-RS-ConfigNZPId-NR.

qcl-DMRSgroup1-CSI-RS-parameter-NR

qcl-DMRSgroup2-CSI-RS-parameter-NR

qcl-DMRSgroup1-SSblock-Index-NR.

qcl-DMRSgroup2-SSblock-Index-NR.

qcl-DMRSgroup1-SSblock-parameter-NR

qcl-DMRSgroup2-SSblock-parameter-NR

qcl-DMRSgroup1-PTRS-ConfigId-NR.

qcl-DMRSgroup2-PTRS-ConfigId-NR.

qcl-DMRSgroup1-PTRS-parameter-NR

qcl-DMRSgroup2-PTRS-parameter-NR

qcl-DMRSgroup1-TRS-ConfigId-NR.

qcl-DMRSgroup2-TRS-ConfigId-NR.

qcl-DMRSgroup1-TRS parameter-NR

qcl-DMRSgroup2-TRS-parameter-NR

PDCCH resource mapping may be use with quasi-colocation of antennaports. A UE may be configured, for example, with up to 8 parameter setscontaining the QCL information of the DMRS for PDCCH by higher layersignaling to decode future PDCCH per a detected PDCCH with DCI(s)intended for the UE.

The UE may use the parameter set list in the DCIs according to the valueof the PDCCH Quasi-Co-Location Indicator field (mapping defined in Table17 of the Appendix for 1 bit field scenario, Table 18 of the Appendixfor 2 bits field scenario, Table 19 of the Appendix for 3 bits fieldscenario) in the detected PDCCH with DCIs in slot n for determining theQCL relationship of the DMRS for PDCCH with other reference signalsapplied in slot n+k where k may be specified in the spec or configuredby higher layer signaling.

A UE may be configured with one or two DMRS port group(s) based on thenumber of PDCCH that is monitored. When a UE is configured with one DMRSport group, if the PDCCH Quasi-Co-Location Indicator field is 1 bit,state ‘0’ is configured; if the PDCCH Quasi-Co-Location Indicator fieldis 2 bits, one of the state ‘00’, ‘01’ is configured; if the PDCCHQuasi-Co-Location Indicator field is 3 bits, one of the state ‘000’,‘001’, ‘010’, ‘011’ is configured. Each state refers to one RS set,which indicates a QCL relationship for the DMRS port group.

When a UE is configured with two DMRS port groups, if the PDCCHQuasi-Co-Location Indicator field is 1 bit, state ‘1’ is configured; ifthe PDCCH Quasi-Co-Location Indicator field is 2 bits, one of the state‘10’, configured; if the PDCCH Quasi-Co-Location Indicator field is 3bits, one of the state ‘100’, ‘101’, ‘110’, ‘111’ is configured. Eachstate refers to two RS sets where each RS set indicates a QCLrelationship for one of the two DMRS port groups of the UE respectively.

With different value of the PDCCH Quasi-Co-Location Indicator fieldconfigured, the UE may determine the QCL information for each DMRS portgroup such as which RS(s) is QCL-ed and the QCL-ed parameters for eachRS from the parameters in the corresponding parameter set configured viahigher layer signaling. Note, there may be one or more RS(s) with sameor different types in a RS set. If there are more than one RS in a RSset, each of them may associated with different QCL parameters.

A set or subset of the DCI PDCCH Quasi-Co-Location Indicator fieldparameters in Table 17, Table 18 and Table 19 may be added into thecurrent LTE DCI format 0/1/1A/1B/1C/1D/2/2A/2B/2C for indicating QCL forPDCCH DMRS. However, a set or subset of the above DCI parameters may bealso used to form a new DCI format, for example a DCI format forindicating QCL for PDCCH DMRS.

For one DMRS port group configured case, one or more of the followingparameters for determining PDCCH antenna port quasi co-location areconfigured via higher layer signaling for each parameter set:

qcl-CSI-RS-ConfigNZPId-NR.

qcl-CSI-RS-parameter-NR

qcl-SSblock-Index-NR.

qcl-SSblock-parameter-NR

For two DMRS port groups configured case, one or more of the followingparameters for determining PDCCH antenna port quasi co-location areconfigured via higher layer signaling for each parameter set:

qcl-DMRSgroup1-CSI-RS-ConfigNZPId-NR.

qcl-DMRSgroup2-CSI-RS-ConfigNZPId-NR.

qcl-DMRSgroup1-CSI-RS-parameter-NR

qcl-DMRSgroup2-CSI-RS-parameter-NR

qcl-DMRSgroup1-SSblock-Index-NR.

qcl-DMRSgroup2-SSblock-Index-NR.

qcl-DMRSgroup1-SSblock-parameter-NR

qcl-DMRSgroup2-SSblock-parameter-NR

The UE may perform QCL checking if, for example, a single bitQuasi-Co-Location checking Indicator field (mapping defined in Table 20of the Appendix) in a corresponding PDCCH with DCI intended for the UEis set to 1.

A set or subset of the DCI Quasi-Co-Location checking Indicator fieldparameters in Table 20 may be added into the current LTE DCI format0/1/1A/1B/1C/1D/2/2A/2B/2C for QCL checking. However, a set or subset ofthe above DCI parameters may be also used to form a new DCI format, forexample a DCI format for QCL checking.

One or more of the following parameters for performing Quasi-Co-Locationchecking are configured via higher layer signaling for the thresholdset:

qcl-AverageGain-Threshold-NR

qcl-DopplerShift-Threshold-NR

qcl-DopplerSpread-Threshold-NR

qcl-AverageDelay-Threshold-NR

qcl-DelaySpread-Threshold-NR

A UE performing Quasi-Co-Location checking may determine if theconfigured QCL relationship still holds or not. The UE estimates theconfigured QCL parameters for each RS within a RS set and the DMRS inthe corresponding DMRS port group. If all the difference of theestimated QCL parameters is within the threshold, the UE determine theconfigured QCL relationship holds. If any of the difference of theestimated QCL parameters exceeds the threshold, the UE determine theconfigured QCL relationship not hold. The UE reports to gNB/TRP and mayassume any QCL relationship until next PDCSH Quasi-Co-Location Indicatoris configured. If a UE is configured with two DMRS port groups, it mayperform the Quasi-Co-Location checking for the two DMRS port groupsseparately.

A UE may perform aperiodic CSI-RS transmission if, for example, a singlebit Aperiodic CSI-RS triggering indicator field in a corresponding PDCCHwith DCI intended for the UE is set to 1.

When the Aperiodic CSI-RS triggering indicator, field configured to a UEis set to 1, the UE is configured with up to 4 aperiodic CSI-RSresources by higher layer signaling to decode PDSCH per a detectedPDCCH. The UE may use the aperiodic CSI-RS resource per the value of the‘Aperiodic CSI-RS resource indicator’ field (mapping defined in Table 21of the Appendix) in the detected PDCCH for determining the PDSCH REmapping.

A set or subset of the DCI Aperiodic CSI-RS resource indicator fieldparameters in Table 21 may be added into the current LTE DCI format0/1/1A/1B/1C/1D/2/2A/2B/2C for Aperiodic CSI-RS configuration. However,a set or subset of the above DCI parameters may be also used to form anew DCI format, for example a DCI format for Aperiodic CSI-RSconfiguration.

Each Aperiodic CSI-RS resource may be configured with N out of K NZP/ZPCSI-RS resources or resource sets for aperiodic CSI-RS transmission viahigher layer signaling. Each Aperiodic CSI-RS resource may be alsoconfigured with the QCL information of the N configured NZP/ZP CSI-RSvia the higher layer signaling if it is needed. The QCL informationincludes the reference signal (may be one or more in same or differenttypes.) and the parameters that are QCL-ed associated with eachreference signal (for different RS, the QCL-ed parameters may bedifferent).

A UE may perform aperiodic Interference Measurement Resourcetransmission if, for example, a single bit aperiodic interferencemeasurement resource (IMR) triggering indicator field in a correspondingPDCCH with DCI intended for the UE is set to 1.

When the Aperiodic interference measurement resource (IMR) triggeringindicator field configured to a UE is set to 1, the UE is configuredwith up to 4 aperiodic zero-power CSI-RS resources by higher layersignaling to measure the interference of other TRP/gNB per a detectedPDCCH. The UE may use the aperiodic non-zero-power CSI-RS resource perthe value of the ‘Aperiodic non-zero-power CSI-RS resource indicator’field in the detected PDCCH for determining the PDSCH RE mapping.

DCI may be adjusted to support BWP. The following signaling may becarried in DCI by either enhancing existing DCI field or new DCI format(the number of bits needed and description are shown in Table 22 of theAppendix):

BWP activation flag: indication of changing BWP

Reference point: starting begin of BW (in PRB)

BWP bandwidth: active bandwidth (in PRBs)

PDSCH starting symbol: PDSCH starting symbol in a slot.

DCI may be adjusted to support multiple TRPs or Panels. A UE may beconfigured up to N parameter sets lists by RRC and/or MAC-CE signalingto decode multiple PDSCHs by a detected PDCCH with the DCI intended forthe UE and the given serving cell. The UE may use the parameter set listper the value of the PDSCH and Quasi-Co-Location Indicator field in thedetected PDCCH with DCI for determining PDSCH antenna port quasico-location and COREST of monitoring single co-schedule PDCCH ormultiple PDCCHs. See Table 23 of the Appendix.

Parameter set n configured by RRC and/or MAC-CE may include one or moreof the following parameters:

a cell/TRP's TRS position (number of ports and frequency shift);

a cell/TRP's numerology, slot and subframe configuration;

a zero-power CSI-RS (CSI-IM) configuration;

a value of PDSCH starting symbol;

a CSI-RS resource index for DMRS quasi-co-location;

a cell/TRP's SS burst set location; and

CORESET locations for monitoring single PDCCH or multiple PDCCHs.

The 3rd Generation Partnership Project (3GPP) develops technicalstandards for cellular telecommunications network technologies,including radio access, the core transport network, and servicecapabilities—including work on codecs, security, and quality of service.Recent radio access technology (RAT) standards include WCDMA (commonlyreferred as 3G), LTE (commonly referred as 4G), and LTE-Advancedstandards. 3GPP has begun working on the standardization of nextgeneration cellular technology, called New Radio (NR), which is alsoreferred to as “5G”. 3GPP NR standards development is expected toinclude the definition of next generation radio access technology (newRAT), which is expected to include the provision of new flexible radioaccess below 6 GHz, and the provision of new ultra-mobile broadbandradio access above 6 GHz. The flexible radio access is expected toconsist of a new, non-backwards compatible radio access in new spectrumbelow 6 GHz, and it is expected to include different operating modesthat can be multiplexed together in the same spectrum to address a broadset of 3GPP NR use cases with diverging requirements. The ultra-mobilebroadband is expected to include cmWave and mmWave spectrum that mayprovide the opportunity for ultra-mobile broadband access for, e.g.,indoor applications and hotspots. In particular, the ultra-mobilebroadband is expected to share a common design framework with theflexible radio access below 6 GHz, with cmWave and mmWave specificdesign optimizations.

3GPP has identified a variety of use cases that NR is expected tosupport, resulting in a wide variety of user experience requirements fordata rate, latency, and mobility. The use cases include the followinggeneral categories: enhanced mobile broadband (e.g., broadband access indense areas, indoor ultra-high broadband access, broadband access in acrowd, 50+ Mbps everywhere, ultra-low cost broadband access, mobilebroadband in vehicles), critical communications, massive machine typecommunications, network operation (e.g., network slicing, routing,migration and interworking, energy savings), and enhancedvehicle-to-everything (eV2X) communications. Specific service andapplications in these categories include, e.g., monitoring and sensornetworks, device remote controlling, bi-directional remote controlling,personal cloud computing, video streaming, wireless cloud-based office,first responder connectivity, automotive ecall, disaster alerts,real-time gaming, multi-person video calls, autonomous driving,augmented reality, tactile internet, and virtual reality to name a few.All of these use cases and others are contemplated herein.

FIG. 1A illustrates one embodiment of an example communications system100 in which the methods and apparatuses described and claimed hereinmay be embodied. As shown, the example communications system 100 mayinclude wireless transmit/receive units (WTRUs) 102 a, 102 b, 102 c,and/or 102 d (which generally or collectively may be referred to as WTRU102), a radio access network (RAN) 103/104/105/103 b/104b/105b, a corenetwork 106/107/109, a public switched telephone network (PSTN) 108, theInternet 110, and other networks 112, though it will be appreciated thatthe disclosed embodiments contemplate any number of WTRUs, basestations, networks, and/or network elements. Each of the WTRUs 102 a,102 b, 102 c, 102 d, 102 e may be any type of apparatus or deviceconfigured to operate and/or communicate in a wireless environment.Although each WTRU 102 a, 102 b, 102 c, 102 d, 102 e is depicted inFIGS. 1A-1E as a hand-held wireless communications apparatus, it isunderstood that with the wide variety of use cases contemplated for 5Gwireless communications, each WTRU may comprise or be embodied in anytype of apparatus or device configured to transmit and/or receivewireless signals, including, by way of example only, user equipment(UE), a mobile station, a fixed or mobile subscriber unit, a pager, acellular telephone, a personal digital assistant (PDA), a smartphone, alaptop, a tablet, a netbook, a notebook computer, a personal computer, awireless sensor, consumer electronics, a wearable device such as a smartwatch or smart clothing, a medical or eHealth device, a robot,industrial equipment, a drone, a vehicle such as a car, truck, train, orairplane, and the like.

The communications system 100 may also include a base station 114 a anda base station 114 b. Base stations 114 a may be any type of deviceconfigured to wirelessly interface with at least one of the WTRUs 102 a,102 b, 102 c to facilitate access to one or more communication networks,such as the core network 106/107/109, the Internet 110, and/or the othernetworks 112. Base stations 114 b may be any type of device configuredto wiredly and/or wirelessly interface with at least one of the RRHs(Remote Radio Heads) 118 a, 118 b and/or TRPs (Transmission andReception Points) 119 a, 119 b to facilitate access to one or morecommunication networks, such as the core network 106/107/109, theInternet 110, and/or the other networks 112. RRHs 118 a, 118 b may beany type of device configured to wirelessly interface with at least oneof the WTRU 102 c, to facilitate access to one or more communicationnetworks, such as the core network 106/107/109, the Internet 110, and/orthe other networks 112. TRPs 119 a, 119 b may be any type of deviceconfigured to wirelessly interface with at least one of the WTRU 102 d,to facilitate access to one or more communication networks, such as thecore network 106/107/109, the Internet 110, and/or the other networks112. By way of example, the base stations 114 a, 114 b may be a basetransceiver station (BTS), a Node-B, an eNode B, a Home Node B, a HomeeNode B, a site controller, an access point (AP), a wireless router, andthe like. While the base stations 114 a, 114 b are each depicted as asingle element, it will be appreciated that the base stations 114 a, 114b may include any number of interconnected base stations and/or networkelements.

The base station 114 a may be part of the RAN 103/104/105, which mayalso include other base stations and/or network elements (not shown),such as a base station controller (BSC), a radio network controller(RNC), relay nodes, etc. The base station 114 b may be part of the RAN103 b/104b/105b, which may also include other base stations and/ornetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), relay nodes, etc. The base station 114 amay be configured to transmit and/or receive wireless signals within aparticular geographic region, which may be referred to as a cell (notshown). The base station 114 b may be configured to transmit and/orreceive wired and/or wireless signals within a particular geographicregion, which may be referred to as a cell (not shown). The cell mayfurther be divided into cell sectors. For example, the cell associatedwith the base station 114 a may be divided into three sectors. Thus, inan embodiment, the base station 114 a may include three transceivers,e.g., one for each sector of the cell. In an embodiment, the basestation 114 a may employ multiple-input multiple output (MIMO)technology and, therefore, may utilize multiple transceivers for eachsector of the cell.

The base stations 114 a may communicate with one or more of the WTRUs102 a, 102 b, 102 c over an air interface 115/116/117, which may be anysuitable wireless communication link (e.g., radio frequency (RF),microwave, infrared (IR), ultraviolet (UV), visible light, cmWave,mmWave, etc.). The air interface 115/116/117 may be established usingany suitable radio access technology (RAT).

The base stations 114 b may communicate with one or more of the RRHs 118a, 118 b and/or TRPs 119 a, 119 b over a wired or air interface 115b/116b/117b, which may be any suitable wired (e.g., cable, opticalfiber, etc.) or wireless communication link (e.g., radio frequency (RF),microwave, infrared (IR), ultraviolet (UV), visible light, cmWave,mmWave, etc.). The air interface 115 b/116b/117b may be establishedusing any suitable radio access technology (RAT).

The RRHs 118 a, 118 b and/or TRPs 119 a, 119 b may communicate with oneor more of the WTRUs 102 c, 102 d over an air interface 115 c/116c/117c,which may be any suitable wireless communication link (e.g., radiofrequency (RF), microwave, infrared (IR), ultraviolet (UV), visiblelight, cmWave, mmWave, etc.). The air interface 115 c/116c/117c may beestablished using any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 103/104/105 and the WTRUs 102a, 102 b, 102 c, or RRHs 118 a, 118 b and TRPs 119 a, 119 b in the RAN103 b/104b/105b and the WTRUs 102 c, 102 d, may implement a radiotechnology such as Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access (UTRA), which may establish the air interface115/116/117 or 115 c/116c/117c respectively using wideband CDMA (WCDMA).WCDMA may include communication protocols such as High-Speed PacketAccess (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-SpeedDownlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access(HSUPA).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c, or RRHs 118 a, 118 b and TRPs 119 a, 119 b in the RAN 103 b/104b/105band the WTRUs 102 c, 102 d, may implement a radio technology such asEvolved UMTS Terrestrial Radio Access (E-UTRA), which may establish theair interface 115/116/117 or 115 c/116c/117c respectively using LongTerm Evolution (LTE) and/or LTE-Advanced (LTE-A). In the future, the airinterface 115/116/117 may implement 3GPP NR technology.

In an embodiment, the base station 114 a in the RAN 103/104/105 and theWTRUs 102 a, 102 b, 102 c, or RRHs 118 a, 118 b and TRPs 119 a, 119 b inthe RAN 103 b/104b/105b and the WTRUs 102 c, 102 d, may implement radiotechnologies such as IEEE 802.16 (e.g., Worldwide Interoperability forMicrowave Access (WiMAX)), CDMA2000, CDMA2000 1x, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 c in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, and the like. In anembodiment, the base station 114 c and the WTRUs 102 e, may implement aradio technology such as IEEE 802.11 to establish a wireless local areanetwork (WLAN). In an embodiment, the base station 114 c and the WTRUs102 d, may implement a radio technology such as IEEE 802.15 to establisha wireless personal area network (WPAN). In yet another embodiment, thebase station 114 c and the WTRUs 102 e, may utilize a cellular-based RAT(e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocellor femtocell. As shown in FIG. 1A, the base station 114 b may have adirect connection to the Internet 110. Thus, the base station 114 c maynot be required to access the Internet 110 via the core network106/107/109.

The RAN 103/104/105 and/or RAN 103 b/104b/105b may be in communicationwith the core network 106/107/109, which may be any type of networkconfigured to provide voice, data, applications, and/or voice overinternet protocol (VoIP) services to one or more of the WTRUs 102 a, 102b, 102 c, 102 d. For example, the core network 106/107/109 may providecall control, billing services, mobile location-based services, pre-paidcalling, Internet connectivity, video distribution, etc., and/or performhigh-level security functions, such as user authentication.

Although not shown in FIG. 1A, it will be appreciated that the RAN103/104/105 and/or RAN 103 b/104b/105b and/or the core network106/107/109 may be in direct or indirect communication with other RANsthat employ the same RAT as the RAN 103/104/105 and/or RAN 103b/104b/105b or a different RAT. For example, in addition to beingconnected to the RAN 103/104/105 and/or RAN 103 b/104b/105b, which maybe utilizing an E-UTRA radio technology, the core network 106/107/109may also be in communication with another RAN (not shown) employing aGSM radio technology.

The core network 106/107/109 may also serve as a gateway for the WTRUs102 a, 102 b, 102 c, 102 d, 102 e to access the PSTN 108, the Internet110, and/or other networks 112. The PSTN 108 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). The Internet 110 may include a global system ofinterconnected computer networks and devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP) and the internet protocol (IP) inthe TCP/IP internet protocol suite. The networks 112 may include wiredor wireless communications networks owned and/or operated by otherservice providers. For example, the networks 112 may include anothercore network connected to one or more RANs, which may employ the sameRAT as the RAN 103/104/105 and/or RAN 103 b/104b/105b or a differentRAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities, e.g., theWTRUs 102 a, 102 b, 102 c, 102 d, and 102 e may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, the WTRU 102 e shown in FIG. 1Amay be configured to communicate with the base station 114 a, which mayemploy a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

FIG. 1B is a block diagram of an example apparatus or device configuredfor wireless communications in accordance with the embodimentsillustrated herein, such as for example, a WTRU 102. As shown in FIG.1B, the example WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad/indicators 128, non-removable memory 130, removablememory 132, a power source 134, a global positioning system (GPS)chipset 136, and other peripherals 138. It will be appreciated that theWTRU 102 may include any sub-combination of the foregoing elements whileremaining consistent with an embodiment. Also, embodiments contemplatethat the base stations 114 a and 114 b, and/or the nodes that basestations 114 a and 114 b may represent, such as but not limited totransceiver station (BTS), a Node-B, a site controller, an access point(AP), a home node-B, an evolved home node-B (eNodeB), a home evolvednode-B (HeNB), a home evolved node-B gateway, and proxy nodes, amongothers, may include some or all of the elements depicted in FIG. 1B anddescribed herein.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115/116/117. For example, in an embodiment,the transmit/receive element 122 may be an antenna configured totransmit and/or receive RF signals. In an embodiment, thetransmit/receive element 122 may be an emitter/detector configured totransmit and/or receive IR, UV, or visible light signals, for example.In yet an embodiment, the transmit/receive element 122 may be configuredto transmit and receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit and/or receive any combination of wireless signals.

In addition, although the transmit/receive element 122 is depicted inFIG. 1B as a single element, the WTRU 102 may include any number oftransmit/receive elements 122. More specifically, the WTRU 102 mayemploy MIMO technology. Thus, in an embodiment, the WTRU 102 may includetwo or more transmit/receive elements 122 (e.g., multiple antennas) fortransmitting and receiving wireless signals over the air interface115/116/117.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad/indicators 128 (e.g., a liquid crystal display(LCD) display unit or organic light-emitting diode (OLED) display unit).The processor 118 may also output user data to the speaker/microphone124, the keypad 126, and/or the display/touchpad/indicators 128. Inaddition, the processor 118 may access information from, and store datain, any type of suitable memory, such as the non-removable memory 130and/or the removable memory 132. The non-removable memory 130 mayinclude random-access memory (RAM), read-only memory (ROM), a hard disk,or any other type of memory storage device. The removable memory 132 mayinclude a subscriber identity module (SIM) card, a memory stick, asecure digital (SD) memory card, and the like. In an embodiment, theprocessor 118 may access information from, and store data in, memorythat is not physically located on the WTRU 102, such as on a server or ahome computer (not shown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries, solar cells, fuel cells, and thelike.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 115/116/117from a base station (e.g., base stations 114 a, 114 b) and/or determineits location based on the timing of the signals being received from twoor more nearby base stations. It will be appreciated that the WTRU 102may acquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include varioussensors such as an accelerometer, biometrics (e.g., finger print)sensors, an e-compass, a satellite transceiver, a digital camera (forphotographs or video), a universal serial bus (USB) port or otherinterconnect interfaces, a vibration device, a television transceiver, ahands free headset, a Bluetooth® module, a frequency modulated (FM)radio unit, a digital music player, a media player, a video game playermodule, an Internet browser, and the like.

The WTRU 102 may be embodied in other apparatuses or devices, such as asensor, consumer electronics, a wearable device such as a smart watch orsmart clothing, a medical or eHealth device, a robot, industrialequipment, a drone, a vehicle such as a car, truck, train, or airplane.The WTRU 102 may connect to other components, modules, or systems ofsuch apparatuses or devices via one or more interconnect interfaces,such as an interconnect interface that may comprise one of theperipherals 138.

FIG. 1C is a system diagram of the RAN 103 and the core network 106according to an embodiment. As noted above, the RAN 103 may employ aUTRA radio technology to communicate with the WTRUs 102 a, 102 b, and102 c over the air interface 115. The RAN 103 may also be incommunication with the core network 106. As shown in FIG. 1C, the RAN103 may include Node-Bs 140 a, 140 b, 140 c, which may each include oneor more transceivers for communicating with the WTRUs 102 a, 102 b, 102c over the air interface 115. The Node-Bs 140 a, 140 b, 140 c may eachbe associated with a particular cell (not shown) within the RAN 103. TheRAN 103 may also include RNCs 142 a, 142 b. It will be appreciated thatthe RAN 103 may include any number of Node-Bs and RNCs while remainingconsistent with an embodiment.

As shown in FIG. 1C, the Node-Bs 140 a, 140 b may be in communicationwith the RNC 142 a. Additionally, the Node-B 140 c may be incommunication with the RNC 142 b. The Node-Bs 140 a, 140 b, 140 c maycommunicate with the respective RNCs 142 a, 142 b via an Iub interface.The RNCs 142 a, 142 b may be in communication with one another via anIur interface. Each of the RNCs 142 a, 142 b may be configured tocontrol the respective Node-Bs 140 a, 140 b, 140 c to which it isconnected. In addition, each of the RNCs 142 a, 142 b may be configuredto carry out or support other functionality, such as outer loop powercontrol, load control, admission control, packet scheduling, handovercontrol, macro-diversity, security functions, data encryption, and thelike.

The core network 106 shown in FIG. 1C may include a media gateway (MGW)144, a mobile switching center (MSC) 146, a serving GPRS support node(SGSN) 148, and/or a gateway GPRS support node (GGSN) 150. While each ofthe foregoing elements are depicted as part of the core network 106, itwill be appreciated that any one of these elements may be owned and/oroperated by an entity other than the core network operator.

The RNC 142 a in the RAN 103 may be connected to the MSC 146 in the corenetwork 106 via an IuCS interface. The MSC 146 may be connected to theMGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102 a, 102 b,102 c with access to circuit-switched networks, such as the PSTN 108, tofacilitate communications between the WTRUs 102 a, 102 b, 102 c andtraditional land-line communications devices.

The RNC 142 a in the RAN 103 may also be connected to the SGSN 148 inthe core network 106 via an IuPS interface. The SGSN 148 may beconnected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between and the WTRUs102 a, 102 b, 102 c and IP-enabled devices.

As noted above, the core network 106 may also be connected to thenetworks 112, which may include other wired or wireless networks thatare owned and/or operated by other service providers.

FIG. 1D is a system diagram of the RAN 104 and the core network 107according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, and102 c over the air interface 116. The RAN 104 may also be incommunication with the core network 107.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 160 a, 160 b, 160c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In an embodiment,the eNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus,the eNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and receive wireless signals from, the WTRU 102 a.

Each of the eNode-Bs 160 a, 160 b, and 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the uplink and/or downlink, and the like. As shown in FIG. 1D, theeNode-Bs 160 a, 160 b, 160 c may communicate with one another over an X2interface.

The core network 107 shown in FIG. 1D may include a mobility managementgateway (MME) 162, a serving gateway 164, and a packet data network(PDN) gateway 166. While each of the foregoing elements are depicted aspart of the core network 107, it will be appreciated that any one ofthese elements may be owned and/or operated by an entity other than thecore network operator.

The MME 162 may be connected to each of the eNode-Bs 160 a, 160 b, and160 c in the RAN 104 via an Si interface and may serve as a controlnode. For example, the MME 162 may be responsible for authenticatingusers of the WTRUs 102 a, 102 b, 102 c, bearer activation/deactivation,selecting a particular serving gateway during an initial attach of theWTRUs 102 a, 102 b, 102 c, and the like. The MME 162 may also provide acontrol plane function for switching between the RAN 104 and other RANs(not shown) that employ other radio technologies, such as GSM or WCDMA.

The serving gateway 164 may be connected to each of the eNode-Bs 160 a,160 b, and 160 c in the RAN 104 via the Si interface. The servinggateway 164 may generally route and forward user data packets to/fromthe WTRUs 102 a, 102 b, 102 c. The serving gateway 164 may also performother functions, such as anchoring user planes during inter-eNode Bhandovers, triggering paging when downlink data is available for theWTRUs 102 a, 102 b, 102 c, managing and storing contexts of the WTRUs102 a, 102 b, 102 c, and the like.

The serving gateway 164 may also be connected to the PDN gateway 166,which may provide the WTRUs 102 a, 102 b, 102 c with access topacket-switched networks, such as the Internet 110, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and IP-enableddevices.

The core network 107 may facilitate communications with other networks.For example, the core network 107 may provide the WTRUs 102 a, 102 b,102 c with access to circuit-switched networks, such as the PSTN 108, tofacilitate communications between the WTRUs 102 a, 102 b, 102 c andtraditional land-line communications devices. For example, the corenetwork 107 may include, or may communicate with, an IP gateway (e.g.,an IP multimedia subsystem (IMS) server) that serves as an interfacebetween the core network 107 and the PSTN 108. In addition, the corenetwork 107 may provide the WTRUs 102 a, 102 b, 102 c with access to thenetworks 112, which may include other wired or wireless networks thatare owned and/or operated by other service providers.

FIG. 1E is a system diagram of the RAN 105 and the core network 109according to an embodiment. The RAN 105 may be an access service network(ASN) that employs IEEE 802.16 radio technology to communicate with theWTRUs 102 a, 102 b, and 102 c over the air interface 117. As will befurther discussed below, the communication links between the differentfunctional entities of the WTRUs 102 a, 102 b, 102 c, the RAN 105, andthe core network 109 may be defined as reference points.

As shown in FIG. 1E, the RAN 105 may include base stations 180 a, 180 b,180 c, and an ASN gateway 182, though it will be appreciated that theRAN 105 may include any number of base stations and ASN gateways whileremaining consistent with an embodiment. The base stations 180 a, 180 b,180 c may each be associated with a particular cell in the RAN 105 andmay include one or more transceivers for communicating with the WTRUs102 a, 102 b, 102 c over the air interface 117. In an embodiment, thebase stations 180 a, 180 b, 180 c may implement MIMO technology. Thus,the base station 180 a, for example, may use multiple antennas totransmit wireless signals to, and receive wireless signals from, theWTRU 102 a. The base stations 180 a, 180 b, 180 c may also providemobility management functions, such as handoff triggering, tunnelestablishment, radio resource management, traffic classification,quality of service (QoS) policy enforcement, and the like. The ASNgateway 182 may serve as a traffic aggregation point and may beresponsible for paging, caching of subscriber profiles, routing to thecore network 109, and the like.

The air interface 117 between the WTRUs 102 a, 102 b, 102 c and the RAN105 may be defined as an R1 reference point that implements the IEEE802.16 specification. In addition, each of the WTRUs 102 a, 102 b, and102 c may establish a logical interface (not shown) with the corenetwork 109. The logical interface between the WTRUs 102 a, 102 b, 102 cand the core network 109 may be defined as an R2 reference point, whichmay be used for authentication, authorization, IP host configurationmanagement, and/or mobility management.

The communication link between each of the base stations 180 a, 180 b,and 180 c may be defined as an R8 reference point that includesprotocols for facilitating WTRU handovers and the transfer of databetween base stations. The communication link between the base stations180 a, 180 b, 180 c and the ASN gateway 182 may be defined as an R6reference point. The R6 reference point may include protocols forfacilitating mobility management based on mobility events associatedwith each of the WTRUs 102 a, 102 b, 102 c.

As shown in FIG. 1E, the RAN 105 may be connected to the core network109. The communication link between the RAN 105 and the core network 109may defined as an R3 reference point that includes protocols forfacilitating data transfer and mobility management capabilities, forexample. The core network 109 may include a mobile IP home agent(MIP-HA) 184, an authentication, authorization, accounting (AAA) server186, and a gateway 188. While each of the foregoing elements aredepicted as part of the core network 109, it will be appreciated thatany one of these elements may be owned and/or operated by an entityother than the core network operator.

The MIP-HA may be responsible for IP address management, and may enablethe WTRUs 102 a, 102 b, and 102 c to roam between different ASNs and/ordifferent core networks. The MIP-HA 184 may provide the WTRUs 102 a, 102b, 102 c with access to packet-switched networks, such as the Internet110, to facilitate communications between the WTRUs 102 a, 102 b, 102 cand IP-enabled devices. The AAA server 186 may be responsible for userauthentication and for supporting user services. The gateway 188 mayfacilitate interworking with other networks. For example, the gateway188 may provide the WTRUs 102 a, 102 b, 102 c with access tocircuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. In addition, the gateway 188 mayprovide the WTRUs 102 a, 102 b, 102 c with access to the networks 112,which may include other wired or wireless networks that are owned and/oroperated by other service providers.

Although not shown in FIG. 1E, it will be appreciated that the RAN 105may be connected to other ASNs and the core network 109 may be connectedto other core networks. The communication link between the RAN 105 theother ASNs may be defined as an R4 reference point, which may includeprotocols for coordinating the mobility of the WTRUs 102 a, 102 b, 102 cbetween the RAN 105 and the other ASNs. The communication link betweenthe core network 109 and the other core networks may be defined as an R5reference, which may include protocols for facilitating interworkingbetween home core networks and visited core networks.

The core network entities described herein and illustrated in FIGS. 1A,1C, 1D, and 1E are identified by the names given to those entities incertain existing 3GPP specifications, but it is understood that in thefuture those entities and functionalities may be identified by othernames and certain entities or functions may be combined in futurespecifications published by 3GPP, including future 3GPP NRspecifications. Thus, the particular network entities andfunctionalities described and illustrated in FIGS. 1A, 1B, 1C, 1D, and1E are provided by way of example only, and it is understood that thesubject matter disclosed and claimed herein may be embodied orimplemented in any similar communication system, whether presentlydefined or defined in the future.

FIG. 1F is a block diagram of an exemplary computing system 90 in whichone or more apparatuses of the communications networks illustrated inFIGS. 1A, 1C, 1D and 1E may be embodied, such as certain nodes orfunctional entities in the RAN 103/104/105, Core Network 106/107/109,PSTN 108, Internet 110, or Other Networks 112. Computing system 90 maycomprise a computer or server and may be controlled primarily bycomputer readable instructions, which may be in the form of software,wherever, or by whatever means such software is stored or accessed. Suchcomputer readable instructions may be executed within a processor 91, tocause computing system 90 to do work. The processor 91 may be a generalpurpose processor, a special purpose processor, a conventionalprocessor, a digital signal processor (DSP), a plurality ofmicroprocessors, one or more microprocessors in association with a DSPcore, a controller, a microcontroller, Application Specific IntegratedCircuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, anyother type of integrated circuit (IC), a state machine, and the like.The processor 91 may perform signal coding, data processing, powercontrol, input/output processing, and/or any other functionality thatenables the computing system 90 to operate in a communications network.Coprocessor 81 is an optional processor, distinct from main processor91, that may perform additional functions or assist processor 91.Processor 91 and/or coprocessor 81 may receive, generate, and processdata related to the methods and apparatuses disclosed herein.

In operation, processor 91 fetches, decodes, and executes instructions,and transfers information to and from other resources via the computingsystem's main data-transfer path, system bus 80. Such a system busconnects the components in computing system 90 and defines the mediumfor data exchange. System bus 80 typically includes data lines forsending data, address lines for sending addresses, and control lines forsending interrupts and for operating the system bus. An example of sucha system bus 80 is the PCI (Peripheral Component Interconnect) bus.

Memories coupled to system bus 80 include random access memory (RAM) 82and read only memory (ROM) 93. Such memories include circuitry thatallows information to be stored and retrieved. ROMs 93 generally containstored data that cannot easily be modified. Data stored in RAM 82 can beread or changed by processor 91 or other hardware devices. Access to RAM82 and/or ROM 93 may be controlled by memory controller 92. Memorycontroller 92 may provide an address translation function thattranslates virtual addresses into physical addresses as instructions areexecuted. Memory controller 92 may also provide a memory protectionfunction that isolates processes within the system and isolates systemprocesses from user processes. Thus, a program running in a first modecan access only memory mapped by its own process virtual address space;it cannot access memory within another process's virtual address spaceunless memory sharing between the processes has been set up.

In addition, computing system 90 may contain peripherals controller 83responsible for communicating instructions from processor 91 toperipherals, such as printer 94, keyboard 84, mouse 95, and disk drive85.

Display 86, which is controlled by display controller 96, is used todisplay visual output generated by computing system 90. Such visualoutput may include text, graphics, animated graphics, and video. Thevisual output may be provided in the form of a graphical user interface(GUI). Display 86 may be implemented with a CRT-based video display, anLCD-based flat-panel display, gas plasma-based flat-panel display, or atouch-panel. Display controller 96 includes electronic componentsrequired to generate a video signal that is sent to display 86.

Further, computing system 90 may contain communication circuitry, suchas for example a network adapter 97, that may be used to connectcomputing system 90 to an external communications network, such as theRAN 103/104/105, Core Network 106/107/109, PSTN 108, Internet 110, orOther Networks 112 of FIGS. 1A, 1B, 1C, 1D, and 1E, to enable thecomputing system 90 to communicate with other nodes or functionalentities of those networks. The communication circuitry, alone or incombination with the processor 91, may be used to perform thetransmitting and receiving steps of certain apparatuses, nodes, orfunctional entities described herein.

It is understood that any or all of the apparatuses, systems, methodsand processes described herein may be embodied in the form of computerexecutable instructions (e.g., program code) stored on acomputer-readable storage medium which instructions, when executed by aprocessor, such as processors 118 or 91, cause the processor to performand/or implement the systems, methods and processes described herein.Specifically, any of the steps, operations or functions described hereinmay be implemented in the form of such computer executable instructions,executing on the processor of an apparatus or computing systemconfigured for wireless and/or wired network communications. Computerreadable storage media include volatile and nonvolatile, removable andnon-removable media implemented in any non-transitory (e.g., tangible orphysical) method or technology for storage of information, but suchcomputer readable storage media do not includes signals. Computerreadable storage media include, but are not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other tangible or physical medium which can be used to store thedesired information and which can be accessed by a computing system.

TABLE 1 Abbreviations ACK Acknowledgement BFRR Beam Failure RecoveryRequest BWP Band Width Part CBG Code Block Group CQI Channel QualityIndicator CRC Cyclic Redundancy Check C-RNTI Cell RNTI CSI-RSChannel-State Information - Reference Signal DCI Downlink ControlInformation DL Downlink DMRS DeModulation Reference Signal eNB EvolvedNode B FDM Frequency Division Multiplex gNB next generation NodeB, 5Gaccess network HARQ Hybrid Automatic Repeat request IMR InterferenceMeasurement Resource LAA Licensed-Assisted Access LTE Long TermEvolution MAC Medium Access Control MAC CE MAC Control Element MCCHMulticast Control Channel MIMO Multiple Input Multiple Output MPDCCH MTCPhysical Downlink Control Channel MTC Machine-Type Communications NACKNegative Acknowledgement NR New Radio OFDM Orthogonal Frequency DivisionMultiplex PDCCH Physical Downlink Control Channel PDSCH PhysicalDownlink Shared Channel PHY Physical Layer PRACH Physical Random AccessChannel PRB Physical Resource Block PSCCH Physical Sidelink ControlChannel PSSCH Physical Sidelink Shared Channel PUCCH Physical UplinkControl Channel PUSCH Physical Uplink Shared Channel QCLQuasi-Co-Location RAN Radio Access Network (3GPP) RAT Radio AccessTechnology (3GPP) RB Resource Block RBG Resource Block Group RNTI RadioNetwork Temporary Identifier RRC Radio Resource Control SCell SecondaryCell SCI Sidelink Control Information SC-MCCH Single Cell-MCCH SI SystemInformation SIMO Single Input Multiple Output SPS-RNTI Semi-PersistentScheduling RNTI TA Timing Advance TDD Time Division Duplex TMTransmission Mode TPC Transmit Power Control TRA Time ResourceAllocation TRP Transmission and Reception Point UE User Equipment ULUplink

TABLE 2 Parameters for Time Resource Allocation Parameters BitsDescription BWP 0/ Slot/Subframe 1 Either Slot or Subframe aggregationis configured via RRC message. TRP 0/ Aggregation 0: no aggregationCarrier 0/ Flag 1: aggregation RAT 0 Note: if this flag is notpresented, it is default to no aggregation, for example slot or subframebased scheduling Slot 0/ n_(slot) 1) The slot index referenced fromSubframe 0 or • Current subframe, for example 1 ms time boundary, Indexn_(sf) n_(slot) = 0 bit: for subframe reference with 15k SubcarrierSpacing (SC), for example one 14-symbol slot in a subframe. n_(slot) = 1bit: for subframe reference with 30k Subcarrier Spacing (SC), forexample two 14-symbol slots in a subframe with the slot index values asthe follows  ∘ “0” for Slot 0  ∘ “1” for Slot 1. n_(slot) = 2 bits forsubframe reference with 60k Subcarrier Spacing (SC), for example four14-symbol slots in a subframe with the slot index values as the follows ∘ “00” for Slot 0  ∘ “01” for Slot 1  ∘ “10” for Slot 2  ∘ “11” forSlot 3 n_(slot) = 3 bits for subframe reference with 120k SubcarrierSpacing (SC), for example eight 14-symbol slots in a subframe with theslot index values as the follows  ∘ “000” for Slot 0  ∘ “001” for Slot 1 ∘ . . .  ∘ “111” for Slot 7 n_(slot) = 4 bits for subframe referencewith 120k Subcarrier Spacing (SC), for example sixteen 14-symbol slotsin a subframe with the slot index values as the follows  ∘ “0000” forSlot 0  ∘ “0001” for Slot 1  ∘ . . .  ∘ “1111” for Slot 15. • NR-PDCCHcarrying this DCI The bits n_(slot) and the slot index values aresimilar to the above examples referenced to the current subframe •System Frame Number (SFN), for example 10 ms time boundary The n bitsmay be n_(subframe) + 4, where the n_(subframe) is the bits referencedfrom current subframe. 2) The subframe index referenced from • CurrentSystem Frame Number (SFN), for example 10 ms time boundary For example,the bits n_(sf) may be 4, with the subframe index values as the follows ∘ “0000” for Subframe 0  ∘ “0001” for Subframe 1  ∘ . . .  ∘ “1001” forSubframe 9. Note: if this field is not presented, it is default tocurrent slot or subframe. Symbol n_(sym) 1) Contiguous Allocation: forexample, n_(sym) = 8 Allocation Where 4 bits for Start Symbol/OffsetIndex referenced from the slot/subframe within Slot 0/ or the PDCCHcarrying the DCI. The index value may be Subframe 0  ∘ “0000” for Symbol0  ∘ “0001” for Symbol 1  ∘ . . .  ∘ “1101” For Symbol 13. • Where 4bits for End Symbol/Symbol Range within a slot/subframe. The index valuemay be  ∘ “0000” for Symbol 0/range = 1 symbol  ∘ “0001” for Symbol1/range = 2 symbols  ∘ . . .  ∘ “1101” For Symbol 13/range = 14 symbols.2) Periodic Allocation: for example, n_(sym) = 9 • 4 bits for StartSymbol/Offset Index referenced from the slot/subframe or the PDCCHcarrying the DCI • 3 bits for symbols allocated contiguously  ∘ “000”for 0 symbol  ∘ “001” for 1 symbol  ∘ . . .  ∘ “111” For 7 symbols • 2bits for period with the following values as an example  ∘ “00” for 2symbols  ∘ “01” for 3 symbols  ∘ “10” for 4 symbols  ∘  “11” For 6symbols. 3) Distributed Segmented: for example, n_(sym) = 10~12 • 4~5bits for Segment 1 which contains 2~3 bits for Start Symbol referencedfrom the slot/subframe or the NR-PDCCH carrying the DCI and 2 bits forSegment Range • 4~5 bits for Segment 2 which contains 2~3 bits for StartSymbol reference from the end of the gap and 2 bits Symbol Range • 2bits for Gap in symbols 4) Distributed Bitmap: for example, n_(sym) = 14Where total 14 bits each represent a symbol within a 14-symbol slot,where the MSB for Symbol 0 and LSB for Symbol 13. Value “0” for notallocated, and value “1” for allocated. For example, “11110_01110_0011”is for allocation at symbol 0~3, symbol 6~8, and symbol 12~13. Slot 1/n_(slot1) Same as the Slot 0/Subframe 0 Subframe 1 or Notes: Indexn_(sf1) 1) For current slot/subframe scheduling, this field is notneeded. 2) For slot/subframe aggregated scheduling, this field is notneeded if the time resource allocation pattern is the same as the Slot0/Subframe 0. Symbol n_(sym1) Same as the Slot 0/Subframe 0 AllocationNotes: within Slot 1/ 1) For current slot/subframe scheduling, thisfield is not needed. Subframe 1 2) For slot/subframe aggregatedscheduling, this field is not needed if the time resource allocationpattern is the same as the Slot 0/Subframe 0. Slot 2/ n_(slot2) Same asthe Slot 0/Subframe 0 Subframe 2 or Index n_(sf2) . . . . . . . . . BWP1/ Slot 0/ n_(slot11) Same as the BWP 0/TRP 0/Carrier 0/RAT 0 TRP 1/Subframe 0 or Notes: Carrier 1/ Index n_(sf11) 1) For currentslot/subframe scheduling, this field is not needed if the time resourceRAT 1 allocation pattern is the same as the BWP 0/TRP 0/Carrier 0/RAT 0.Symbol n_(sym11) Same as the BWP 0/TRP 0/Carrier 0/RAT 0 AllocationNotes: within Slot 0/ For current slot/subframe scheduling, this fieldis not needed if the time resource Subframe 0 allocation pattern is thesame as the BWP 0/TRP 0/Carrier 0/RAT 0. . . . . . . . . .

TABLE 3 Parameters for Frequency Resource Allocation Parameters BitsDescription BWP 0/ BWP 1 For inter-BWP hopping: “0” hopping within aBWP; “1” hopping TRP 0/ Hopping between BWPs. Carrier 0/ Flag Note: ifthis flag is not presented, it is default to no inter-BWP hopping. RAT 0Slot 1 “0” no slot hopping; “1” slot hopping between BWPs. Hopping Note:if this flag is not presented, it is default to no slot hopping FlagHopping 3 MSB is for inter-slot with “1” or intra-slot hopping with “0”.The Pattern following is an example of the possible values. “0_00”:intra-slot hopping type 0 . . . “0_11”: intra-slot hopping type 3“1_00”: inter-slot hopping type 0 . . . “1_11”: inter-slot hopping type3 Note: if this flag is not presented, no hopping is enabled PRB/ n 1)Contiguous Allocation with PRB/RBG RBG • Total n = n_(PRB) bits for PRBallocation depending on the size of Allocation allocated bandwidth orBWP,  n_(PRB) = n_(PRBstart) + n_(PRBend)/n_(PRBrange), wheren_(PRBstart) is for start PRB index or frequency offset in PRBsreferenced from PRB 0 of the system band, n_(PRBend) is for end PRBindex referenced from the start PRB or n_(PRBrange) is the range in PRBfrom the start PRB. • Total n = n_(RBG) bits for RBG allocationdepending on the size of allocated bandwidth or BWP,  n_(RBG) =n_(RBGstart) − n_(RBGend)/n_(RBGrange), where n_(RBGstart) is for startRBG index or frequency offset in RBGs referenced from PRB 0 of thesystem band, n_(RBGend) is for end RBG index referenced from the startRBG or n_(RBGrange) is the range in RBG from the start RBG. Note: therelationship between PRB and RBG is as the follows  n_(RBG) = n_(PRB) −log₂ (RBG_size), where RBG = PRB with RBG_size = 1, RBG = 2 PRBs withRBG_size = 2, RBG = 4 PRBs with RBG_size = 4, etc. 2) Contiguous orNoncontiguous Allocation with RBG Bitmap, for example the type 0 for LTEDL resource allocation. See, for example, 3GPP TS 36.213, Physical layerprocedures (Release 14), V14.3.0. 3) Contiguous or NoncontiguousAllocation with RBG Set Based, for example the type 1 for LTE DLresource allocation. See, for example, 3GPP TS 36.213 4) Contiguous orNoncontiguous Allocation with Virtual RB (VRB), for example the type 2for LTE DL “Localized” for contiguous and “Distributed” fornoncontiguous. See, for example, 3GPP TS 36.213 Note: for UL DFT-s-OFDMwaveform, only contiguous allocation is used, and for UL CP-OFDMwaveform, both contiguous and noncontiguous allocation may be used asthe DL frequency resource allocation. BWP 1/ Slot 1 Same as the BWP0/TRP 0/Carrier 0/RAT 0 TRP 1/ Hopping Note: this field is not needed ifthe frequency resource allocation Carrier 1/ Flag pattern is the same asthe BWP 0/TRP 0/Carrier 0/RAT 0. RAT 1 Hopping 3 Same as the BWP 0/TRP0/Carrier 0/RAT 0 Pattern Note: this field is not needed if thefrequency resource allocation pattern is the same as the BWP 0/TRP0/Carrier 0/RAT 0. PRB/ n1 Same as the BWP 0/TRP 0/Carrier 0/RAT 0 RBGNote: this field is not needed if the frequency resource allocationAllocation pattern is the same as the BWP 0/TRP 0/Carrier 0/RAT 0.

TABLE 4 Parameters for Time Resource Allocation of Mini-slot(s)Parameters Bits Description Slot 0 Slot 0 Index n_(slot) See Table 2 andassociated discussion of time resource allocation. Mini-slotn_(minis) 1) One or Repeated Mini-slot Allocation Allocation Then_(minis) may contain the following sub-fields. For example, within Slot0  n_(ministart): 2~4 bits for the symbol index of the start location ofthe  first mini-slot within the slot referenced from the slot or the NR-PDCCH carrying the DCI.  n_(minilength): 2~3 bits for the length insymbols of the mini-slot in  symbol(s) referenced from the start symbol. n_(minigap): 1~2 bits for the gap in symbols between repeated mini- slots in symbol(s) referenced from the previous mini-slot. n_(minirepeat): 2~3 bits for the repeated mini-slots within a slot. For example, “0” is for no repeat, “1” is for repeat once, etc. 2) PeriodicMini-slot Allocation The n_(minis) may contain the following sub-fields.For example,  n_(minitstart): 2~4 bits for the symbol index of the startlocation of  the first mini-slot within the slot referenced from theslot or the  NR-PDCCH carrying the DCI.  n_(minilength): 1~2 bits forthe length in symbols of the mini-slot in  symbol(s) referenced from thestart symbol.  n_(miniperiod): 2~3 bits for the period in symbolsbetween repeated  mini-slots in symbol(s) referenced from the previousmini-slot. 3) Distributed Mini-slot Allocation The n_(minis) may be 14bits for mini-slot bitmap. For example, “00011_10110_1110” is formini-slot 0 with symbol 3~5, mini- slot with symbol 7~8, and mini-slotwith symbol 10~12. Slot 1 Slot 1 Index n_(slot1) Same as the Slot 0Note: this field is not needed if the mini-slot allocation pattern isthe same as the slot 0. Mini-slot n_(minis1) Same as the Slot 0Allocation Note: this field is not needed if the mini-slot allocationpattern is the within Slot 1 same as the slot 0.

TABLE 5 Parameters for CBG Transmission Parameters Bits Description Slot0 CBG n_(CBGTI) n_(CBGTI) is for bitmap for indicating n_(CBGTI) (Re)/or CBGs' (re)transmission within the slot. transmission n_(CBGFI)n_(CBGFI) is a flag for indicating Indication CBG soft buffer flushingwithin Or the slot. 1 < n_(CBGFI) <= number of CBG Flush the CBGsconfigured if shared Indication with the same field with CBTI. Slot 1CBG n_(CBGTI1) Note: this field is not needed if the (Re)/ or pattern isthe same as the slot 0. transmission n_(CBGFI1) Indication Or CBG FlushIndication

TABLE 6 Example of a DCI for UL Mini-slot DCI Sub-fields Bits Comment ULmini-slot n_(ULmini) UL mini-slot allocation for one or multiplemini-slots Allocation within the current slot or next few slots, asdescribed previously for the DCI field used for Mini-slot allocation inreference to Table 4. Frequency 1 “0” for no frequency hopping; “1” forinter-mini-slot Hopping Flag frequency hopping. Frequency n_(hop)Inter-mini-slot frequency hopping patterns. Hopping Typically, n_(hop) =2~3 bits. Pattern UL Resource n_(PRBminiUL) Contiguous or noncontiguousPRB/RBG allocation block or as described in reference to Table 3 forassignment n_(RBGminiUL) frequency resource allocation. Note: contiguousallocation may be used for DFT-s-OFDM waveform and both contiguous andnoncontiguous allocation may be used for PC-OFDM waveform MCS and RV 5Modulation and coding scheme and redundancy version NDI (New Data 1 Toindicate a new data transmission or not Indicator) HARQ process n_(HARQ)HARQ process number, typically n_(HARQ) = 2~3. number TPC for PUSCH 2Transmit power control command for scheduled PUSCH or PUCCH Cyclic shiftfor 3 Cyclic shift for DM RS and OCC index and DM RS IFDMA configurationUL SPS n_(SPS) For UE's UL SPS configuration, typically n_(SPS) = 3bits. configuration index CSI request n_(CSI) For UE's CSI-RSmeasurement report configuration index, typically n_(CSI) = 3~4. SRSrequest 0~1 Used for scheduling a PUSCH transmission with SRS or not.

TABLE 7 Example of a DCI for DL Mini-slot DCI Sub-fields Bits Comment DLmini-slot N_(DLmini) DL mini-slot allocation for one or multiplemini-slots Allocation within the current slot or next few slots, asdescribed previously for the DCI field used for Mini-slot allocation inreference to Table 4. DL Resource n_(PRBminiDL) Contiguous ornoncontiguous PRB/RBG allocation as block or described in reference toTable 3. for frequency assignment n_(RBGminiDL) resource allocation. MCS5 Modulation and coding scheme HARQ Process 3 HARQ process number NDI 1New data indicator RV 2 Redundancy version TPC for PUCCH 2 Transmitpower control for PUCCH HARQ-ACK n_(HARQr) HARQ/ACK resource allocation,typically n_(HARQr) = 2 resource TPMI n_(TPMI) Transmitted PrecodingMatrix Indicator (TPMI) information for precoding PMI n_(PMI) PrecodingMatrix Indicator (PMI) confirmation for precoding DL Reference n_(DLRS)DL RS configuration for measurements used for beam Signal (RS)management, mobility management, Channel Stat Configuration Informationmeasurement, time and/or frequency tracking and correction, etc.Typically, n_(DLRS) = 4~6 bits.

TABLE 8A Example of a DCI for UL Group Common PDCCH DCI Sub-fields BitsComment Slot Format n_(SFIindex) Index of a lookup table containing allIndication the possible configurations of a slot in (SFI) terms of DLsymbols, UL symbols, gap, and reserved, and/or unknown symbols. Reservedbits n_(reserved) Bits reserved for forward compatibility

TABLE 8B Example of a DCI for SFI over Multiple Slots in a Group CommonPDCCH DCI Sub-fields Bits Comment Slot Format n_(SFIindex) Index of alookup table containing all the Indication possible configurations of aslot in terms index (SFI) of DL symbols, UL symbols, gap, and reserved,and/or unknown symbols. Reserved bits n_(reserved) Bits reserved forforward compatibility Number of slots n_(slots) Applicable to 2^(nslots)slots

TABLE 8C Example of a Preemption Indication through Group Common PDCCHDCI Sub-fields Bits Comment x symbols n_(x) log₂(x_(max)) bits areconfigured to indicate number of contiguous symbols pre-empted. x <=x_(max) Starting symbol n_(st, symb) n_(st, symbol) is a symbol indexwithin a slot. number For example, it goes from 0 to 13 in a 14-symbolslot. y RBs n_(y) log₂(y_(max)) bits are configured to indicate numberof RBs. y <= y_(max) Starting RB n_(st, RB) n_(st, RB) is a RB indexwithin a BWP. number within a reference BWP

TABLE 8D Example of a Preemption Indication through Group Common PDCCHDCI Sub-fields Bits Comment Starting symbol n_(st, symb) n_(st, symbol)is an index within a slot. number For example, it goes from 0 to 13 in a14-symbol slot. Starting RB n_(st, RB) n_(st, RB) is a RB index within anumber within BWP. a reference BWP

TABLE 8E Example of a Preemption Indication through Group Common PDCCHDCI Sub-fields Bits Comment Starting symbol n_(st, symb) n_(st, symbol)is an index within a slot. number For example, it goes from 0 to 13 in a14-symbol slot. Starting RB k_(max)*n_(st, RB) n_(st, RB) is a RB indexwithin a set number of up to k_(max) sets in one or within a referencemultiple BWP. When k < k_(max) BWP the extra bits are set to 0

TABLE 9 Example of a DCI Format 0D for Grant-free Resource AllocationDCI Sub-fields Bits Comment Carrier/BWP Indicator 0 or 3 Multi-carriersor BWP indication. Flag for format0D/ 1 “0” for Format 0D format1Adifferentiation Time Resource Allocation n_(time) Contiguous ornoncontiguous time resource allocation. See Table 1 and associateddiscussion. An example is described below specifically for Grant-freetype 2.  n_(time) bits for time resource allocation for Grant-free which may contain the following bits.  • n_(start): start symbol indexor time offset referenced from the slot or subframe boundary or theNR-PDCCH carrying the DCI for activation.  • n_(symb): end symbol indexor the length in symbols for time resource allocation  • n_(period): theperiod in symbols for periodic time allocation within a slot orsubframe. Example: for a 14-symbol slot, the periodic time allocationmay be as such, starting from symbol 3, allocated 3 symbols, thenrepeated with period of 5 symbols within the slot. Notes:  • Bothn_(symb) and n_(period) may also be configured by the RRC, but thedynamically signaled value overrides the statically configured values. • If n_(period) is not presented, it's a contiguous allocation withn_(start) and n_(symb). Frequency Hopping Flag 1 “0” for no frequencyhopping; “1” for inter-mini- slot frequency hopping. Frequency HoppingPattern n_(hop) Inter-mini-slot frequency hopping patterns. Typically,n_(hop) = 2~3 bits. Frequency Resource N_(freq) Contiguous ornoncontiguous PRB/REG allocation Allocation may be used as exemplifiedin Table 3. MCS and RV 5 Modulation and coding scheme and redundancyversion NDI (New Data Indicator) 1 Indicate new transmission or not bytoggling the bit. TPC for PUSCH 2 for Grant-free UL power control Cyclicshift for DM RS n for Grant-free UE's DMRS UL SPS configuration index 3for Grant-free UL SPS configuration UL index (TDD only) 3 for Grant-freeUL in TDD Downlink Assignment 2 for Grant-free UL in TDD Index (DAI) CSIrequest (1 or 2 bits: 2 1, 2 for Grant-free UL CSI if configured bit isfor multi carrier) SRS request 3 for Grant-free UL SRS Cyclic ShiftField mapping 1 For Grant-free UE's DMRS for DMRS Beam Indicator 2~4 Toindicate beam association, pairing, and/or QCL, for example beam index,beam pair index, etc. Transport block size 4 Configure the TBS value(s)for each Grant-free resource allocation Repetition number 3 Max.repetition K HARQ process number 3 Support up to 8 HARQs Channel Accesstype 1 Contention or non-contention Channel Access Priority 2 Contentionbased priority accessing Class

TABLE 10A Example of a DCI for Grant-free HARQ-ACK Feedback DCISub-fields Bits Comment HARQ ACK/ 1 “0” for NACK, and “1” for ACK. NACKfeedback HARQ ID n_(HARQ) HARQ_ID may be derived from the time andfrequency resource, for example,  HARQ_ID = (t mod 2^(nfreq) + f ×2^(nfreq)) mod n_(HARQ), or  HARQ_ID = (t × 2^(ntime) + f mod 2^(ntime))mod n_(HARQ), or from time, frequency and UE ID, for example,  HARQ_ID =[(t mod 2^(nfreq) + f × 2^(nfreq)) + UE-ID] mod n_(HARQ)  HARQ_ID = [(t× 2^(ntime) + f mod 2^(ntime)) + UE-ID] mod n_(HARQ), where 2 < n_(freq)< n_(HARQ), 2 < n_(time) < n_(HARQ), t is the time resource ID (forexample a slot and/or symbol index for time resource allocation) and fis the frequency resource ID (for example a PRB or RBG index and offsetfor frequency resource allocation). Typically, 10 < n_(HARQ) < 16 MCSand RV 5 MCS and RV for retransmission. Timing n_(TA) The n_(TA) is forTime Advance feedback. Advance Typically, n_(TA) is around 6 bits. TPCn_(TPC) The n_(TPC) is for closed loop transmit power control feedback.Typically, n_(TPC) is around 1~2 bits.

TABLE 10B Example of a DCI Format 0D for Grant-free Resource Activationand Deactivation Activation Deactivation TPC for PUSCH set to ‘00’ setto ‘00’ Cyclic shift for DM RS set to ‘000’ set to ‘000’ if present ifpresent MCS and RV MSB is set to ‘0’ set to ‘11111’ Resource blockassignment and N/A Set to all ‘1’s hopping resource allocation

TABLE 10C Example of a DCI Field for BFRR Bit field mapped to indexMessage 0 new candidate beam reported in UE's latest BFRR will not beused. 1 new candidate beam reported in UE's latest BFRR will be used.

TABLE 10D Example of a DCI Field for BFRR Bit field mapped to indexMessage 00 The 1^(st) new candidate beam reported in UE's latest BFRRwill be used. 01 The 2^(nd) new candidate beam reported in UE's latestBFRR will be used. 10 The 3^(rd) new candidate beam reported in UE'slatest BFRR will be used. 11 None of new candidate beams reported inUE's latest BFRR will not be used.

TABLE 11 Example of a DCI Format 7A for Response to BFRR DCI Format 7ABits Comment DL TX beam N The number of new candidate confirmation beamsin UE's BFRR ≤ 2^(N-1) CSI-RS allocation ┌log₂ ^(M)┐ + ┌log₂ ^(M)┐indicates one out of the in the DL K1 + N_(CSI-RS) M CSI-RSconfigurations; K1 kits indicates 2^(K1) possible timing offsets;N_(CSI-RS) indicates the number of CSI-RS repetitions. Indication of┌log₂ ^(Q)┐ + K2 ┌log₂ ^(Q)┐ indicates one out of the PUCCH Q PUCCHresources, and K2 resources of the bits indicates one of 2^(K2) PUCCHformat used for resources indices. beam reporting The timing offset K3or 0 bits Indicates one of 2^(K3) possible timing of beam reporting(implicit) offsets of beam reporting Number of beam 0 or K4 bits For 0bits, the number of beam reporting reporting equals to a numberspecified in the standards, say 1. Otherwise, it indicates one of 2^(K4)possible numbers of beam reporting UE ID 16 UE ID such as C-RNTI,SPS-CRNTI etc.

TABLE 12 Example of a DCI Format 7B for UL TX Beam Change DCI Format 7BBits Comment UL TX beam 1 or 2 Indication of new UL TX beam changeindication change or not, and known at the gNB or needs more measurementof SRS ULnew TX beam P Indicates one of 2P UL TX beams (identified bycorresponding UL SRS) SRS transmission ┌log₂ ^(R)┐ + ┌log₂ ^(R)┐indicates one out of the K5 M SRS configurations. K5 indicates 2^(K5)possible timing offsets. Number of SRS 0 or K6 bits For 0 bits, thenumber of SRS on a transmission given UL TX beam equals to a numberspecified in the standards, say 1. Otherwise, it indicates one of 2^(K6)possible numbers of SRS transmission. UE ID 16 UE ID such as C-RNTI,SPS-CRNTI etc.

TABLE 13 Number of bits and description for DCI fields DCI field nameBits Description PDSCH Quasi-Co- 1 or 2 or 3 Each state corresponding toa Location Indicator set of RS(s) that is QCL-ed with DMRS for PDSCHPDCCH Quasi-Co- 1 or 2 or 3 Each state corresponding to a LocationIndicator set of RS(s) that is QCL-ed with DMRS for PDCCHQuasi-Co-Location 1 Flag for QCL checking checking Indicator occasionAperiodic CSI-RS 1 Flag for Aperiodic CSI-RS triggering indicatortriggering Aperiodic CSI-RS 2 Each state corresponding to an resourceindicator Aperiodic CSI-RS resources for Aperiodic CSI-RS transmissionAperiodic interference 1 Flag for Aperiodic interference measurementmeasurement resource (IMR) resource (IMR) triggering triggeringindicator

TABLE 14 PDSCH Quasi-Co-Location Indicator field in DCI using 1 bitValue of ‘PDSCH Quasi-Co-Location Indicator’ field Description ‘0’Parameter set 1 configured by higher layers ‘1’ Parameter set 2configured by higher layers

TABLE 15 PDSCH Quasi-Co-Location Indicator field in DCI using 2 bitsValue of ‘PDSCH Quasi-Co-Location Indicator’ field Description ‘00’Parameter set 1 configured by higher layers ‘01’ Parameter set 2configured by higher layers ‘10’ Parameter set 3 configured by higherlayers ‘11’ Parameter set 4 configured by higher layers

TABLE 16 PDSCH Quasi-Co-Location Indicator field in DCI using 3 bitsValue of ‘PDSCH Quasi-Co-Location Indicator’ field Description ‘000’Parameter set 1 configured by higher layers ‘001’ Parameter set 2configured by higher layers ‘010’ Parameter set 3 configured by higherlayers ‘011’ Parameter set 4 configured by higher layers ‘100’ Parameterset 5 configured by higher layers ‘101’ Parameter set 6 configured byhigher layers ‘110’ Parameter set 7 configured by higher layers ‘111’Parameter set 8 configured by higher layers

TABLE 17 PDCCH Quasi-Co-Location Indicator field in DCI using 1 bitValue of ‘PDCCH Quasi-Co-Location Indicator’ field Description ‘0’Parameter set 1 configured by higher layers ‘1’ Parameter set 2configured by higher layers

TABLE 18 PDCCH Quasi-Co-Location Indicator field in DCI using 2 bitsValue of ‘PDCCH Quasi-Co-Location Indicator’ field Description ‘00’Parameter set 1 configured by higher layers ‘01’ Parameter set 2configured by higher layers ‘10’ Parameter set 3 configured by higherlayers ‘11’ Parameter set 4 configured by higher layers

TABLE 19 PDCCH Quasi-Co-Location Indicator field in DCI using 3 bitsValue of ‘PDCCH Quasi-Co-Location Indicator’ field Description ‘000’Parameter set 1 configured by higher layers ‘001’ Parameter set 2configured by higher layers ‘010’ Parameter set 3 configured by higherlayers ‘011’ Parameter set 4 configured by higher layers ‘100’ Parameterset 5 configured by higher layers ‘101’ Parameter set 6 configured byhigher layers ‘110’ Parameter set 7 configured by higher layers ‘111’Parameter set 8 configured by higher layers

TABLE 20 Quasi-Co-Location checking Indicator field in DCI Value of‘Quasi-Co- Location checking Indicator’ field Description ‘0’ NO QCLchecking is indicated ‘1’ QCL checking is indicated with threshold setconfigured by higher layers

TABLE 21 Aperiodic CSI-RS resource indicator field in DCI Value of‘Aperiodic CSI-RS resource indicator’ field Description ‘00’ AperiodicCSI-RS resources 1 configured by higher layers ‘01’ Aperiodic CSI-RSresources 2 configured by higher layers ‘10’ Aperiodic CSI-RS resources3 configured by higher layers ‘11’ Aperiodic CSI-RS resources 4configured by higher layers

TABLE 22 Number of bits and description for DCI fields DCI field nameBits Description BWP activation 1 Activation of BWP: 0: disable 1:enable Reference point n bits Starting (PRB) address BWP bandwidth mbits active bandwidth (in PRBs) PDSCH starting symbol 4 bits PDSCHstarting symbol (in a slot)

TABLE 23 PDSCH Quasi-Co-Location Indicator field in DCI using N bitsValue of ‘PDSCH and Quasi-Co- Location Indicator’ field Description 00 .. . 0 Parameter set 1 configured by RRC and/ or MAC-CE . . . Parameterset n configured by RRC and/ or MAC-CE . . . Parameter set n + 1configured by RRC and/ or MAC-CE . . . . . . 11 . . . 1 Parameter set Nconfigured by RRC and/ or MAC-CE

What is claimed:
 1. A User Equipment (UE) comprising: circuitryconfigured to monitor a first configuration for a first controlindication, the first control indication pertaining to a first set oftime and frequency resources for a first data transmission, wherein thefirst set of time and frequency resources are allocated as a jointcontrol resource set with a first control indication transmitted in aPhysical Downlink Control Channel (PDCCH); monitor a secondconfiguration for a plurality of second control indications, the secondcontrol indication pertaining to a second set of time and frequencyresources for a second data transmission, wherein each of the second setof time and frequency resources is allocated as a separate controlresource set with each of the plurality of second control indicationstransmitted in separate PDCCH, wherein each of the first controlindication and the plurality of second control indications comprise (i)Code Block Group (CBG) transmission indication or CBG flush indication,(ii) a Slot Format Indication (SFI), and (iii) a pre-emption indicationfor the first set of time and frequency resources or the second set oftime and frequency resources; and receive downlink data transmission inaccordance with the first control indication or the plurality of secondcontrol indications.
 2. The UE of claim 1, wherein the first datatransmission and the second data transmission are multi-linktransmissions comprising a multi-Bandwidth Parts (multi-BWP), amulti-Transmission/Reception Point (multi-TRP), a multi-carrier, or amulti-Radio Access Technology (multi-RAT) transmission.
 3. The UE ofclaim 2, wherein at least one of the first data transmission and thesecond data transmission is a multi-BWP transmission, and at least oneof the first control indication and the plurality of second controlindications comprises a BWP indication.
 4. The UE of claim 1, wherein atleast one of the first control indication and the plurality of thesecond control indications comprises a mini-slot in a UE specificsearching space.
 5. A method for a network system, the methodcomprising: transmitting a first configuration for a first controlindication pertaining to a first set of time and frequency resources fora first data transmission wherein the first set of time and frequencyresources are allocated as a joint control resource set with a firstcontrol indication transmitted in a Physical Downlink Control Channel(PDCCH); transmitting a second configuration for a plurality of secondcontrol indications pertaining to a second set of time and frequencyresources for a second data transmission for a secondTransmission/Reception Point (TRP) in a second cell, wherein each of thesecond set of time and frequency resources is allocated as a separatecontrol resource set with each of the plurality of second controlindications transmitted in separate PDCCH, wherein each of the firstcontrol indication and the plurality of second control indicationscomprise (i) Code Block Group (CBG) transmission indication or CBG flushindication, (ii) a Slot Format Indication (SFI), and (iii) a pre-emptionindication for the first set of time and frequency resources or thesecond set of time and frequency resources; and sending, to a UserEquipment (UE), downlink data transmission in accordance with the firstcontrol indication or the plurality of second control indications. 6.The method of claim 5, wherein the first data transmission and thesecond data transmission are multi-link transmissions comprising amulti-Bandwidth Parts (multi-BWP), a multi-Transmission/Reception Point(multi-TRP), a multi-carrier, or a multi-Radio Access Technology(multi-RAT) transmission.
 7. The method of claim 6, wherein at least oneof the first data transmission and the second data transmission is amulti-BWP transmission, and at least one of the first control indicationand the plurality of second control indications comprises a BWPindication.
 8. The method of claim 5, wherein at least one of the firstcontrol indication and the plurality of the second control indicationscomprises a mini-slot in a UE specific searching space.
 9. A networkapparatus comprising a circuitry configured to: transmit a configurationfor a first control indication or a plurality of second controlindications, the first control indication pertaining to a first set oftime and frequency resources for a first data transmission, wherein thefirst set of time and frequency resources are allocated as a jointcontrol resource set with a first control indication transmitted in aPhysical Downlink Control Channel (PDCCH), and the second controlindication pertaining to a second set of time and frequency resourcesfor a second data transmission, wherein each of the second set of timeand frequency resources is allocated as a separate control resource setwith each of the plurality of second control indications transmitted inseparate PDCCH, wherein each of the first control indication and theplurality of second control indications comprise (i) Code Block Group(CBG) transmission indication or CBG flush indication, (ii) a SlotFormat Indication (SFI), and (iii) a pre-emption indication for thefirst set of time and frequency resources or the second set of time andfrequency resources; and receive downlink data transmission inaccordance with the first control indication or the plurality of secondcontrol indications.
 10. The network apparatus of claim 9, wherein thefirst data transmission and the second data transmission are multi-linktransmissions comprising a multi-Bandwidth Parts (multi-BWP), amulti-Transmission/Reception Point (multi-TRP), a multi-carrier, or amulti-Radio Access Technology (multi-RAT) transmission.
 11. The networkapparatus of claim 10, wherein at least one of the first datatransmission and the second data transmission is a multi-BWPtransmission, and at least one of the first control indication and theplurality of second control indications comprises a BWP indication. 12.The network apparatus of claim 9, wherein at least one of the firstcontrol indication and the plurality of the second control indicationscomprises a mini-slot in a UE specific searching space.